Skip to content

Commit e031a9a

Browse files
authored
Merge pull request #8652 from iamzili/add-warning-pod-level-stanza
docs: Document VPA incompatibility with pod-level resources stanza
2 parents 38e0fc9 + f494675 commit e031a9a

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

vertical-pod-autoscaler/README.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,11 @@ The Vertical Pod Autoscaler consists of three parts. The recommender, updater an
4545

4646
You can also read about the [features](./docs/features.md) and [known limitations](./docs/known-limitations.md) of the VPA.
4747

48+
> [!IMPORTANT]
49+
> At the moment, VPA is not compatible with workloads that define pod-level `resources` stanzas. Work has started to add pod-level resources support for VPA, for more details see [AEP-7571](https://github.com/kubernetes/autoscaler/pull/8586). Users of VPA may encounter the following issues if they enable VPA for a workload with a pod-level resources stanza defined:
50+
> * When the admission-controller tries to set a container-level limit higher than the pod-level limit, the operation is prohibited, and the pod will not be created.
51+
> * When the admission-controller tries to set the newly recommended container-level requests, their total value cannot exceed the pod-level request or limit. For example, if the pod-level memory request is 100Mi, but the newly recommended total of container-level requests is 250Mi, the pod will fail to be created.
52+
4853
## Related links
4954

5055
- [Design proposal](https://github.com/kubernetes/design-proposals-archive/blob/main/autoscaling/vertical-pod-autoscaler.md)

0 commit comments

Comments
 (0)