-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VPA: add document behavior for Requests & Limits #7927
base: master
Are you sure you want to change the base?
Conversation
Hi @novahe. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
cc @adrianmoisey ( if you wanna take a look too ). |
8089956
to
0252209
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! lgtm from me.
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: novahe, omerap12 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thank you for your thorough review; it has been very beneficial to me. |
/lgtm |
/ok-to-test |
@@ -244,3 +245,15 @@ The `--webhook-labels` parameter for the VPA admission-controller can be used to | |||
When running in EKS with Cilium, the EKS API server cannot route traffic to the overlay network. The VPA admission-controller | |||
Pods either need to use host networking or be exposed through a service or ingress. | |||
See the [Cilium Helm installation page](https://docs.cilium.io/en/stable/installation/k8s-install-helm/) for more info. | |||
|
|||
### Why does VPA fail to create a Pod when resource limits are explicitly set to 0? | |||
VPA currently handles requests=0 and limits=0 inconsistently with Kubernetes, leading to invalid Pod configurations. Here’s the breakdown: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one more change, could you make it clear that if a pod is created with requests=limits=0, that it will break and not work?
It's kind of implied here, but I think it needs to be explicitly called out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I agree ( this is why we opened this issue to begin with :) )
/lgtm cancel |
Hey @novahe, are you still working on this PR? |
What type of PR is this?
/kind documentation
/area vertical-pod-autoscaler
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #7895
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: