Update index.md
parent
0bc2efe4d2
commit
1e40f9fea5
|
@ -26,7 +26,7 @@ The autoscaler is implemented as a control loop.
|
||||||
It periodically queries CPU utilization for the pods it targets.
|
It periodically queries CPU utilization for the pods it targets.
|
||||||
(The period of the autoscaler is controlled by `--horizontal-pod-autoscaler-sync-period` flag of controller manager.
|
(The period of the autoscaler is controlled by `--horizontal-pod-autoscaler-sync-period` flag of controller manager.
|
||||||
The default value is 30 seconds).
|
The default value is 30 seconds).
|
||||||
Then, it compares the arithmetic mean of the pods' CPU utilization with the target and adjust the number of replicas if needed.
|
Then, it compares the arithmetic mean of the pod's CPU utilization with the target and adjust the number of replicas if needed.
|
||||||
|
|
||||||
CPU utilization is the recent CPU usage of a pod divided by the sum of CPU requested by the pod's containers.
|
CPU utilization is the recent CPU usage of a pod divided by the sum of CPU requested by the pod's containers.
|
||||||
Please note that if some of the pod's containers do not have CPU request set,
|
Please note that if some of the pod's containers do not have CPU request set,
|
||||||
|
@ -90,7 +90,7 @@ The cluster has to be started with `ENABLE_CUSTOM_METRICS` environment variable
|
||||||
### Pod configuration
|
### Pod configuration
|
||||||
|
|
||||||
The pods to be scaled must have cAdvisor-specific custom (aka application) metrics endpoint configured. The configuration format is described [here](https://github.com/google/cadvisor/blob/master/docs/application_metrics.md). Kubernetes expects the configuration to
|
The pods to be scaled must have cAdvisor-specific custom (aka application) metrics endpoint configured. The configuration format is described [here](https://github.com/google/cadvisor/blob/master/docs/application_metrics.md). Kubernetes expects the configuration to
|
||||||
be placed in `definition.json` mounted via a [config map](/docs/user-guide/configmap/) in `/etc/custom-metrics`. A sample config map may look like this:
|
be placed in `definition.json` mounted via a [configMap](/docs/user-guide/configmap/) in `/etc/custom-metrics`. A sample config map may look like this:
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
apiVersion: v1
|
apiVersion: v1
|
||||||
|
|
Loading…
Reference in New Issue