-
Notifications
You must be signed in to change notification settings - Fork 697
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
Update assertions for kubelet-client-cert|key rules #12366
Update assertions for kubelet-client-cert|key rules #12366
Conversation
/test |
@rhmdnd: The
Use
In response to this:
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-sigs/prow repository. |
/test 4.17-e2e-aws-ocp4-cis |
🤖 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: |
@rhmdnd #12311 also updated rule See: 4.17-e2e-aws-ocp4-pci-dss-4-0
|
cd32877
to
24fef5b
Compare
/test 4.17-e2e-aws-ocp4-cis |
We recently enabled these rules for 4.17, but didn't update the 4.17 assertion files for FedRAMP High, FedRAMP Moderate, PCI-DSS, or CIS. This commit does that so that so the tests assert the correct behavior on 4.17. ComplianceAsCode#12311
24fef5b
to
6c3503f
Compare
/test 4.17-e2e-aws-ocp4-cis |
Code Climate has analyzed commit 6c3503f 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.5% (0.0% change). View more on Code Climate. |
/test 4.17-e2e-aws-ocp4-cis |
1 similar comment
/test 4.17-e2e-aws-ocp4-cis |
/packit retest-failed |
/retest |
1 similar comment
/retest |
@rhmdnd: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
The prow tests are falling to come up, but the changes look good to me. |
We recently enabled these rules for 4.17, but didn't update the 4.17
assertion files for STIG, FedRAMP High, FedRAMP Moderate, or CIS. This
commit does that so that so the tests assert the correct behavior on
4.17.
#12311