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

Daemonset container and initContainer can run only in privleged mode for daemonset-mps-control-daemon #763

Open
kndoni opened this issue Jun 11, 2024 · 2 comments

Comments

@kndoni
Copy link

kndoni commented Jun 11, 2024

Notes

Dear team.

I noticed following issue on daemonset-mps-control-daemon.yml. There is one container and initContainer that can run only in privileged mode true. But in security context when implementing security policies like for example with kyverno, privileged should be set to false by default and capabilities might be added.

Can you please take this issue in consideration. I have created one PR but I don't think the PR will solve this issue completely in mps daemonset

#756

@kndoni
Copy link
Author

kndoni commented Jun 11, 2024

This issue appears only in mps daemonset, in device-plugin and gdf daemonset I have tested locally and changes in PR are working fine.

Only issue is in mps daemonset that container is running in privileged mode

@kndoni
Copy link
Author

kndoni commented Jun 12, 2024

I added in the PR a value called devicePluginMps so we can controll weather we want MPS to be enabled or not

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

No branches or pull requests

1 participant