-
Notifications
You must be signed in to change notification settings - Fork 807
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
Selinux Mount Option #2253
base: master
Are you sure you want to change the base?
Selinux Mount Option #2253
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
Code Coverage DiffThis PR does not change the code coverage |
flake (kops failed to create cluster) /retest |
/retest lots of flakes today |
2acf2f6
to
32f6bda
Compare
Signed-off-by: Connor Catlett <conncatl@amazon.com>
32f6bda
to
2eefc58
Compare
/retest |
@@ -342,6 +342,9 @@ controller: | |||
# Enable dnsConfig for the controller and node pods | |||
dnsConfig: {} | |||
node: | |||
# Enable SELinux-only optimizations on the EBS CSI Driver node pods | |||
# Must only be set true if all linux nodes in the DaemonSet have SELinux enabled |
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.
Non-blocking comment: Do we want to recommend additional daemonsets feature in-line here.
An extra sentence like: "Please rely on additional daemonsets feature if this is not the case."
What type of PR is this?
/kind feature
What is this PR about? / Why do we need it?
Adds a new helm parameter,
node.selinux
, that mounts the relevant directories to allow the selinux-awaremount
binary to perform selinux-specific optimizations. (This parameter can also be used in the future for any other selinux optimizations on the node).This must be a parameter that is default-disabled, because
/sys/fs/selinux
will not exist unless SELinux is actually enabled on the nodes.How was this change tested?
CI/Manually
Does this PR introduce a user-facing change?