You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/workloads/autoscaling.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,15 @@ Mode | Description
81
81
`Off` | The VPA does not automatically change the resource requirements of the pods. The recommendations are calculated and can be inspected in the VPA object.
82
82
{{< /table >}}
83
83
84
+
### Autoscaling based on cluster size
85
+
86
+
For workloads that need to be scaled based on the size of the cluster (for example
87
+
`cluster-dns` or other system components), you can use the _Cluster Proportional Autoscaler_.<br />
88
+
Just like the VPA, it is not part of the Kubernetes core, but hosted in its
89
+
own repository [on GitHub](https://github.com/kubernetes-sigs/cluster-proportional-autoscaler).
90
+
91
+
The Cluster Proportional Autoscaler watches the number of schedulable {{< glossary_tooltip text="nodes" term_id="node" >}} and cores and scales the number of replicas of the target workload accordingly.
92
+
84
93
### Event driven Autoscaling
85
94
86
95
It is also possible to scale workloads based on events, for example using the
0 commit comments