-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore(helm): enhance securityContext #6523
chore(helm): enhance securityContext #6523
Conversation
@blanchardma, Please address the failed test, which is required to pass to merge the PR. |
7f699b1
to
b2abac7
Compare
Thanks @blanchardma |
b2abac7
to
7464f0c
Compare
@Shubham82 I just squash commits into one. |
/lgtm |
@blanchardma, please resolve the merge conflicts. |
/lgtm |
cc @gjtempleton @mwielgus Thanks! |
@blanchardma please resolve the merge conflict. |
@blanchardma, is there any update on the merge conflict error, please resolve it, so that it will be merged |
d891caf
to
8130bd2
Compare
@gjtempleton @mwielgus @MaciekPytel any chance to get a review? @Shubham82 merge conflicts are solved again. |
charts/cluster-autoscaler/Chart.yaml
Outdated
@@ -11,4 +11,4 @@ name: cluster-autoscaler | |||
sources: | |||
- https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler | |||
type: application | |||
version: 9.37.0 | |||
version: 9.37.1 |
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.
@blanchardma, As this is a new feature request, please bump this into a minor version, not a patch version.
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.
I only bump the patch version because the improvements are commented out and therefore not active, so this is more of a recommendation. But I can adapt it if you stick with it.
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.
@blanchardma, Hi, we update the patch version when there is some bug, but you mention this PR as a feature so I think it should be a minor bump version. So that was my only concern, other than that changes look good to me.
Thanks!
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.
@Shubham82 I fixed the version.
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.
I'd agree with @blanchardma here, it's an example documentation change only, we're not changing the functionality exposed at all, so a patch release increment makes more sense.
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.
I'd agree with @blanchardma here, it's an example documentation change only, we're not changing the functionality exposed at all, so a patch release increment makes more sense.
Thanks, @gjtempleton for clarification.
8130bd2
to
68c3f90
Compare
/lgtm |
Hi @gjtempleton, Needs your approval to merge this PR. Thanks! |
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 the PR, and sorry for being so slow to get to it.
One thing to fix, and then we can get this merged.
/lgtm |
/kind documentation |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: blanchardma, gjtempleton 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 |
What type of PR is this?
/kind feature
/kind cleanup
What this PR does / why we need it:
This pull request improves the securityContext example (commented out) within the Cluster Autoscaler Helm chart values.
These modifications are based on widely accepted security best practices like this.
The runAsUser and runAsGroup will be adjusted from 1001 to 65534, like the other examples in this repo to deploy the Cluster Autoscaler.
Which issue(s) this PR fixes:
Fixes # NONE
Special notes for your reviewer:
NONE
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: