-
Notifications
You must be signed in to change notification settings - Fork 812
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
Fix node.selinux configuration parameter & release Helm Chart v2.39.1 #2311
Fix node.selinux configuration parameter & release Helm Chart v2.39.1 #2311
Conversation
Code Coverage DiffThis PR does not change the code coverage |
note I will cherrypick to release-139 branch. |
f766929
to
d450d62
Compare
d450d62
to
1404536
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.
Validated the warnings are no longer present via helm upgrade --install aws-ebs-csi-driver --namespace kube-system ./charts/aws-ebs-csi-driver --values ./charts/aws-ebs-csi-driver/values.yaml --set node.selinux=true
and that the values are rendered as expected:
kubectl describe pod ebs-csi-node-lfxl8 -n kube-system | grep "selinux-sysfs"
/sys/fs/selinux from selinux-sysfs (ro)
/lgtm
/approve
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil 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 |
/unhold |
/cherry-pick release-1.39 |
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.
/lgtm
/approve
What type of PR is this?
/kind bug
What is this PR about? / Why do we need it?
Fix node.selinux configuration parameter because Pod spec.volumes.hostpath does not have a
readOnly
. That belongs in pod.spec.containers.volumeMounts.When you install via helm this readOnly is dropped with a warning. However this breaks add-on.
How was this change tested?
Does this PR introduce a user-facing change?