Skip two access-control test cases. #1014
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Skipped two test cases related to securityContext.runAsUser field as they both should fail in kind clusters. The reason is those fields are automatically set by SCC in OCP clusters, whereas in kind clusters will be kept as nil in both pod and container level, which is not comformant to best practices.
They started failing in certsuite qe workflow jobs for the PR that fixes the implementation of the runAsUser check:
redhat-best-practices-for-k8s/certsuite#2617