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

genpolicy: add policy support for runAsUser #8879

Open
danmihai1 opened this issue Jan 22, 2024 · 0 comments · May be fixed by #9578
Open

genpolicy: add policy support for runAsUser #8879

danmihai1 opened this issue Jan 22, 2024 · 0 comments · May be fixed by #9578
Assignees
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@danmihai1
Copy link
Contributor

genpolicy doesn't generate correct policy for the K8s YAML filed runAsUser field of SecurityContext and PodSecurityContext.

Example from Kata CI: pod-security-context.yaml

@danmihai1 danmihai1 added bug Incorrect behaviour needs-review Needs to be assessed by the team. no-backport-needed labels Jan 22, 2024
@danmihai1 danmihai1 self-assigned this Jan 22, 2024
danmihai1 added a commit to microsoft/kata-containers that referenced this issue Jan 22, 2024
Add policy support for SecurityContext and PodSecurityContext
runAsUser.

Also, remove outdated UID rule workaround.

Fixes: kata-containers#8879

Signed-off-by: Dan Mihai <dmihai@microsoft.com>
Redent0r pushed a commit to microsoft/kata-containers that referenced this issue Apr 30, 2024
Add policy support for SecurityContext and PodSecurityContext
runAsUser.

Also, remove outdated UID rule workaround.

Fixes: kata-containers#8879

Signed-off-by: Dan Mihai <dmihai@microsoft.com>
@Redent0r Redent0r linked a pull request Apr 30, 2024 that will close this issue
@katacontainersbot katacontainersbot moved this from To do to In progress in Issue backlog Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
Issue backlog
  
In progress
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants