-
Notifications
You must be signed in to change notification settings - Fork 706
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
Re-enable runtime check on network related sysctls #11722
Re-enable runtime check on network related sysctls #11722
Conversation
Skipping CI for Draft Pull Request. |
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
This is ready for reviews, the fix on Compliance Operator side works. |
/lgtm |
@rhmdnd @Vincent056 Any volunteers? @yuumasato You'll probably have to rebase this to resolve the CI checks. |
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
I can rebase the PR, but I'd rather have this one merged after ComplianceAsCode/compliance-operator#497 |
When the CO's "scanner" pod has "HostNetwork" option set to true, these sysctls are visible with values matching Host syctls.
2e33816
to
00023fb
Compare
Rebased after merge of ComplianceAsCode/compliance-operator#497 |
Code Climate has analyzed commit 00023fb and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.4% (0.0% change). View more on Code Climate. |
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
/test |
/test e2e-aws-rhcos4-high We should be able to exercise this in the e2e suite now that ComplianceAsCode/compliance-operator#497 landed and should be available through the latest container images in the upstream container registry. |
/test e2e-aws-rhcos4-high |
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
e2e assertions worked as expected:
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-all-accept-ra - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-all-accept-ra matched expected result
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-all-accept-redirects - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-all-accept-redirects matched expected result
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-all-accept-source-route - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-all-accept-source-route matched expected result
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-default-accept-ra - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-default-accept-ra matched expected result
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-default-accept-redirects - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-default-accept-redirects matched expected result
helpers.go:872: Result - Name: e2e-high-worker-sysctl-net-ipv6-conf-default-accept-source-route - Status: PASS - Severity: medium
helpers.go:1060: Rule e2e-high-worker-sysctl-net-ipv6-conf-default-accept-source-route matched expected result
Description:
Rationale:
It seems taht when CO's "scanner" pod has "HostNetwork" option set to true, these sysctls are visible with values matching Host syctls.
Fixes https://issues.redhat.com/browse/OCPBUGS-19690