-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Common flags across VPA components #7312
base: master
Are you sure you want to change the base?
Conversation
Hi @omerap12. 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. |
/ok-to-test |
Is there a way to move this parameter into code? |
AFAIK no, because those parameter are configured inside the klog package |
It seems they're possible to override, something like this seems to work:
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
900d4ab
to
78d7fc5
Compare
Signed-off-by: Omer Aplatony <[email protected]>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
context: #7291 (comment)
We aim to introduce a common flags package to be used across all VPA components (updater, recommender, and admission-controller), consolidating shared configuration options. Currently, arguments are passed using CMD in the Dockerfile, which can lead to improper behavior when users specify custom arguments. By removing this and setting default values under containers.x.args, we eliminate the problematic behavior described above.
Which issue(s) this PR fixes:
Fixes #7291
Special notes for your reviewer:
If approved, we will need to update the VPA chart to include the default arguments (currently specified in the Dockerfile).
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: