-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Add the ability to better pass additional arguments to containers #1664
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
Conversation
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.
What is the purpose of this change? You are changing the build infrastructure for VPA ...
OK, I noticed the bug in the description, but I'm not sure what is your plan in modifying the build scripts. |
@mwielgus So if I have to customize the arguments to be passed to the containers, then I have to change in Its pod's DockerFile( Recommender, Admission Controller, Updater)? |
You are changing the wrong Docker file. For example you should change this one: Instead of the one that is used to compile stuff. |
Maybe we could move default parameters to CMD as a best practice And there is an extra i at the end of updater |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bskiba The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Any plan to build a new vpa images version to unlock this feature ? |
Hi how can I take advantage of this option? I wanted my VPA to restart pods even when there is only one replica of each. |
#1540