-
Notifications
You must be signed in to change notification settings - Fork 4.3k
VPA chart improvements #8759
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
base: master
Are you sure you want to change the base?
VPA chart improvements #8759
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
|
Welcome @jonkerj! |
|
Hi @jonkerj. Thanks for your PR. I'm waiting for a github.com 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. |
d9ec417 to
8ab9670
Compare
8ab9670 to
6541ff6
Compare
6541ff6 to
0fd9b14
Compare
vertical-pod-autoscaler/charts/vertical-pod-autoscaler/values.yaml
Outdated
Show resolved
Hide resolved
30e10f6 to
e483bad
Compare
56d780f to
4818f01
Compare
Signed-off-by: Jorik Jonker <[email protected]>
4818f01 to
8260fce
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jonkerj 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 |
What type of PR is this?
What this PR does / why we need it:
The current chart does not support configuring
priorityClassName,could have much tighter security settingsand does not allow customization of security settings.It should fit the Pod Security Standard.restrictedafter this PR tooWhich issue(s) this PR fixes:
If needed, I can create issues for these
Special notes for your reviewer:
Does this PR introduce a user-facing change?
no
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
n/a