-
Notifications
You must be signed in to change notification settings - Fork 5
chore: add heritage=deckhouse label for Pods in user ns #1880
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
base: main
Are you sure you want to change the base?
Conversation
|
Workflow has started. The target step completed with status: failure. |
168c4ce to
e012c26
Compare
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. |
e012c26 to
44e4967
Compare
Support security hardening for Deckhouse system components implemented by deckhouse/deckhouse#16749 Add heritage=deckhouse label to Pods that run in user namespaces: - dvcr-importer-* - dvcr-uploader-* - bounder-* Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: Ivan Mikheykin <[email protected]>
Signed-off-by: Ivan Mikheykin <[email protected]>
44e4967 to
a4f3663
Compare
|
Workflow has started. The target step completed with status: failure. |
|
Workflow has started. The target step completed with status: failure. |
Signed-off-by: Ivan Mikheykin <[email protected]>
|
Workflow has started. The target step completed with status: failure. |
Description
Add heritage=deckhouse label to Pods that run in user namespaces:
Also add label to kubevirt and cdi related Pods:
cdi #27
kubevirt #63
Why do we need it, and what problem does it solve?
Support security hardening for Deckhouse system components implemented by deckhouse/deckhouse#16749
What is the expected result?
Non-system service accounts can't delete Pods created in non-system namespaces by the virtualization module.
Checklist
Changelog entries