Kubernetes Horizontal Pod Autoscaler: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
=Overview= | =Overview= | ||
A pre-requisite, if we intend the autoscaler to monitor resource metrics, a source of [[Metrics_in_Kubernetes#Resource_Metrics|resource metrics]] must be deployed. The simplest source of resource metrics is the [[Kubernetes Metrics Server|metrics server]]. | |||
The horizontal pod autoscalers works with a previously deployed higher level controller that supports scaling ([[Kubernetes_Deployments|deployments]], replica sets, stateful sets). | |||
=HPA Manifest= | =HPA Manifest= | ||
{{Internal|Kubernetes Horizontal Pod Autoscaler Manifest|Horizontal Pod Autoscaler Manifest}} | {{Internal|Kubernetes Horizontal Pod Autoscaler Manifest|Horizontal Pod Autoscaler Manifest}} | ||
Revision as of 22:25, 6 October 2020
External
- https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
- https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/
- https://towardsdatascience.com/kubernetes-hpa-with-custom-metrics-from-prometheus-9ffc201991e
- https://github.com/kubernetes/community/blob/master/contributors/design-proposals/instrumentation/custom-metrics-api.md
Internal
Overview
A pre-requisite, if we intend the autoscaler to monitor resource metrics, a source of resource metrics must be deployed. The simplest source of resource metrics is the metrics server.
The horizontal pod autoscalers works with a previously deployed higher level controller that supports scaling (deployments, replica sets, stateful sets).