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

[run-as-non-root-security-context-pod-level] runAsNonRoot does not necessarily comes directly after securityContext #3511

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

SebGondron
Copy link

This rule will create false positives if runAsNonRoot: true is not placed directly after securityContext. I added the appropriate ellipsis.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Sébastien Gondron seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@SebGondron SebGondron changed the title runAsNonRoot does not necessarily comes directly after securityContext [run-as-non-root-security-context-pod-level ] runAsNonRoot does not necessarily comes directly after securityContext Nov 5, 2024
@SebGondron SebGondron changed the title [run-as-non-root-security-context-pod-level ] runAsNonRoot does not necessarily comes directly after securityContext [run-as-non-root-security-context-pod-level] runAsNonRoot does not necessarily comes directly after securityContext Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants