-
Notifications
You must be signed in to change notification settings - Fork 107
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
Exposing values to enable users to manage the SecurityProfilesOperatorDaemon config #1376
Exposing values to enable users to manage the SecurityProfilesOperatorDaemon config #1376
Conversation
Welcome @rahulroshan-kachchap! |
Hi @rahulroshan-kachchap. Thanks for your PR. I'm waiting for a kubernetes-sigs 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/test-infra repository. |
/ok-to-test Thank you for the contribution @rahulroshan-kachchap! I guess this one deserves a release note, doesn't it? |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1376 +/- ##
=======================================
Coverage 44.13% 44.13%
=======================================
Files 50 50
Lines 5651 5651
=======================================
Hits 2494 2494
Misses 3037 3037
Partials 120 120 |
Updated |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JAORMX, rahulroshan-kachchap 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 |
/easycla |
would it be possible to squash the patches to one to have a leaner commit history? |
btw looks like you also need to run |
b208478
to
365378e
Compare
|
@jhrozek Being this as my first PR , can you please elaborate on this? Where do i need to run make deployments? Do i need to post the result somewhere? |
Sorry, I don't know helm very much so I'm not sure I can help with the contents of the PR. But the gist of it is that during PR verifications, one of the checks that are run is the same thing as if you run Looking at your PR, it looks like you were modifying |
Looks good and happy with everything being disabled by default. Tested and works as expected. However, we still need the commits to be squashed so the changes are a single commit. /lgtm /hold |
f2d8496
to
8de151b
Compare
Squashed commits into one |
Hi @pjbgf , what is the expected date for approving this PR? |
Running the CI tests now, waiting for them to finish before tagging this PR as approved. |
@JAORMX are we good here to close the PR as all the required tests are passing |
spec: | ||
enableSelinux: {{ .Values.enableSelinux }} | ||
enableLogEnricher: {{ .Values.enableLogEnricher }} | ||
enableAppArmor: {{ .Values.enableAppArmor }} |
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 would expose also other flags in here such as: enableBpfRecoder
, verbosity
, enableProfiling
. The same all switched off by default.
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.
@ccojocar Will add enableBpfRecorder & enableProfiling.
For verbosity crd says:
verbosity:
description: Verbosity specifies the logging verbosity of the daemon.
type: integer
Since its type is integer, i assume the default needs to be set as 0. Please suggest
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.
@ccojocar kindly suggest
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.
+1
considering the title of the PR I think that would make sense.
But also happy for that to be added as a follow-up PR.
f4e5513
to
022bd4f
Compare
f89f7e1
to
6454c27
Compare
|
064654d
to
3ca5892
Compare
@rahulroshan-kachchap would you mind rebasing this PR again please? |
3ca5892
to
ab40a78
Compare
@rahulroshan-kachchap thank you for following-up and rebasing. 🙇 /lgtm |
What type of PR is this?
kind feature
What this PR does / why we need it:
Expanding helm chart to expose values to enable users to manage the SecurityProfilesOperatorDaemon config, so that users can toggle what's deployed more easily via three new values: enableSelinux, enableLogEnricher and enableAppArmor.
Added config.yaml file in the templates directory of helm chart which takes configurable input from users via values.yaml.
Which issue(s) this PR fixes:
Fixes #1320
Does this PR have test?
NA
Special notes for your reviewer:
Tested the above changes with only enableAppArmor: true and enableSelinux, enableLogEnricher as false. Verified in the spod logs after deployment:
I1213 04:41:53.620891 2231997 apparmorprofile.go:277] apparmor-spod "msg"="detecting apparmor support..."
I1213 04:41:53.642182 2231997 apparmorprofile.go:284] apparmor-spod "msg"="apparmor enabled: OK"
I1213 04:41:53.642412 2231997 apparmorprofile.go:287] apparmor-spod "msg"="apparmor enforceable: OK"
Does this PR introduce a user-facing change?