chore: add heritage=deckhouse label for Pods in user ns #1880
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Workflow has started. The target step completed with status: failure. |
diafour
force-pushed
the
chore/api/add-heritage-deckhouse-label
branch
from
01ee7ba to
168c4ce
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 <ivan.mikheykin@flant.com>
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
Signed-off-by: Ivan Mikheykin <ivan.mikheykin@flant.com>
diafour
force-pushed
the
chore/api/add-heritage-deckhouse-label
branch
from
168c4ce to
e012c26
Compare
diafour
added
e2e/run
Contributor
|
Workflow has started. The target step completed with status: failure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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