@@ -18,6 +18,12 @@ of a running pod without restarting the pod or its containers. A Kubernetes node
18
18
allocates resources for a pod based on its ` requests ` , and restricts the pod's
19
19
resource usage based on the ` limits ` specified in the pod's containers.
20
20
21
+ Changing the resource allocation for a running Pod requires the
22
+ ` InPlacePodVerticalScaling ` [ feature gate] ( /docs/reference/command-line-tools-reference/feature-gates/ )
23
+ to be enabled. The alternative is to delete the Pod and let the
24
+ [ workload controller] ( /docs/concepts/workloads/controllers/ ) make a replacement Pod
25
+ that has a different resource requirement.
26
+
21
27
For in-place resize of pod resources:
22
28
- Container's resource ` requests ` and ` limits ` are _ mutable_ for CPU
23
29
and memory resources.
@@ -45,6 +51,8 @@ For in-place resize of pod resources:
45
51
46
52
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
47
53
54
+ The ` InPlacePodVerticalScaling ` [ feature gate] ( /docs/reference/command-line-tools-reference/feature-gates/ ) must be enabled
55
+ for your control plane and for all nodes in your cluster.
48
56
49
57
## Container Resize Policies
50
58
@@ -170,8 +178,8 @@ spec:
170
178
171
179
# # Updating the pod's resources
172
180
173
- Let's say the CPU requirements have increased, and 0.8 CPU is now desired. This
174
- is typically determined, and may be programmatically applied, by an entity such as
181
+ Let's say the CPU requirements have increased, and 0.8 CPU is now desired. This may
182
+ be specified manually, or determined and programmatically applied by an entity such as
175
183
[VerticalPodAutoscaler](https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler#readme) (VPA).
176
184
177
185
{{< note >}}
0 commit comments