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
As of Kubernetes {{< skew currentVersion >}}, VPA does not support resizing pods in-place, but this
85
-
integration is being worked on. For manually resizing pods in-place, see [Resize Container Resources In-Place](/docs/tasks/configure-pod-container/resize-container-resources/).
84
+
As of Kubernetes {{< skew currentVersion >}}, VPA does not support resizing pods in-place,
85
+
but this integration is being worked on.
86
+
For manually resizing pods in-place, see [Resize Container Resources In-Place](/docs/tasks/configure-pod-container/resize-container-resources/).
86
87
87
88
### Autoscaling based on cluster size
88
89
@@ -99,9 +100,9 @@ If the number of replicas should stay the same, you can scale your workloads ver
99
100
the [_Cluster Proportional Vertical Autoscaler_](https://github.com/kubernetes-sigs/cluster-proportional-vertical-autoscaler).
100
101
The project is **currently in beta** and can be found on GitHub.
101
102
102
-
While the Cluster Proportional Autoscaler scales the number of replicas of a workload, the Cluster Proportional Vertical Autoscaler
103
-
adjusts the resource requests for a workload (for example a Deployment or DaemonSet) based on the number of nodes and/or cores
104
-
in the cluster.
103
+
While the Cluster Proportional Autoscaler scales the number of replicas of a workload,
104
+
the Cluster Proportional Vertical Autoscaler adjusts the resource requests for a workload
105
+
(for example a Deployment or DaemonSet) based on the number of nodes and/or cores in the cluster.
105
106
106
107
### Event driven Autoscaling
107
108
@@ -118,8 +119,8 @@ Another strategy for scaling your workloads is to **schedule** the scaling opera
118
119
reduce resource consumption during off-peak hours.
119
120
120
121
Similar to event driven autoscaling, such behavior can be achieved using KEDA in conjunction with
121
-
its [`Cron` scaler](https://keda.sh/docs/latest/scalers/cron/). The `Cron` scaler allows you to define schedules
122
-
(and time zones) for scaling your workloads in or out.
122
+
its [`Cron` scaler](https://keda.sh/docs/latest/scalers/cron/).
123
+
The `Cron` scaler allows you to define schedules (and time zones) for scaling your workloads in or out.
0 commit comments