Skip to content
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

Rename access control test #1034

Closed
wants to merge 3 commits into from
Closed

Rename access control test #1034

wants to merge 3 commits into from

Conversation

greyerof
Copy link
Contributor

Due to this certsuite PR:
redhat-best-practices-for-k8s/certsuite#2654 ,
the runAsUser and runAsNonRoot securityContext fields check has been
merged into access-control-security-context-run-as-non-root-user-check.

greyerof and others added 3 commits December 20, 2024 10:20
Due to this certsuite PR:
redhat-best-practices-for-k8s/certsuite#2654 ,
the runAsUser and runAsNonRoot securityContext fields check has been
merged into access-control-security-context-run-as-non-root-user-check.
greyerof added a commit to greyerof/certsuite that referenced this pull request Dec 20, 2024
@greyerof
Copy link
Contributor Author

I'll rework the certsuite PR to use the other tc name so we don't need to change this repo.

@greyerof greyerof closed this Dec 20, 2024
bnshr pushed a commit to redhat-best-practices-for-k8s/certsuite that referenced this pull request Dec 23, 2024
…2654)

* Merge runAsUser and runAsNonRoot checks in a single testcase/check.

These two test cases have been merged:
access-control-security-context-run-as-non-root-user-check
access-control-security-context-non-root-user-id-check

As a result, both securityConstraint fields "runAsNonRoot" and
"runAsUser" are checked inside the existing test case
access-control-security-context-run-as-non-root-user-check

To pass the test case, either:
a) runAsUser must be `!= 0` at pod or container level.
b) runAsNonRoot must be `true` at pod or container level.

* Remove access-control-security-context-non-root-user-id-check from expected_results.yaml file.

* QE branch ref set to rename_access_control_test

QE PR
redhat-best-practices-for-k8s/certsuite-qe#1034
is pending to merge but the branch can be used here.

* Use access-control-security-context-non-root-user-id-check.

* Update expected_results.yaml file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant