Update assertions for ingress controller TLS check #12361
Conversation
|
Start a new ephemeral environment with changes proposed in this pull request: Fedora Environment Oracle Linux 8 Environment |
rhmdnd
force-pushed
the
update-assertions-for-ingress-operator-rule
branch
from
7d0345d to
4ec18f4
Compare
|
/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.13-e2e-aws-ocp4-high |
|
🤖 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: |
|
/test 4.16-e2e-aws-ocp4-pci-dss-4-0 |
Nevermind, I see them on #12362 |
|
Actually, the |
|
We recently incorporated a new rule into the CIS profile that checks ingress controller TLS configs: ComplianceAsCode#12220 We added it to the CIS profile, but didn't update the assertions in the moderate or high profiles, which is causing periodic CI to fail. This commit adds the assertion to the moderate and high test files so we're checking it in subsequent CI runs.
rhmdnd
force-pushed
the
update-assertions-for-ingress-operator-rule
branch
from
4ec18f4 to
5f2fca1
Compare
|
/test 4.13-e2e-aws-ocp4-high |
|
Code Climate has analyzed commit 5f2fca1 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. |
|
@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. |
We recently incorporated a new rule into the CIS profile that checks
ingress controller TLS configs:
#12220
We added it to the CIS profile, but didn't update the assertions in the
moderate or high profiles, which is causing periodic CI to fail. This
commit adds the assertion to the moderate and high test files so we're
checking it in subsequent CI runs.