Add securityContext.seccompProfile.type: RuntimeDefault to manager deployment to meet restricted Pod security profile #358
Conversation
This file contains 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
rybnico
requested review from
65278,
avorima,
pborn-ionos,
mcbenjemaa and
wikkyk
as code owners
🚀 e2e tests runWe add labels to the PRs to control the e2e test runs by running specific tests and skipping some test contexts,
ℹ️ Ask a |
|
wikkyk
approved these changes
Dec 10, 2024
rybnico
added a commit
to rybnico/cluster-api-provider-proxmox
that referenced
this pull request
Dec 18, 2024
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 of changes:
The current
securityContextof themanagerdeployment doesn't meet the Pod Security Profile "restricted", which makes it impossible to run in "restricted" namespaces.The
cluster-apideployments also set this value, for example hereTesting performed:
With this change implemented, a deployment to a 'restricted' namespace will be successful. It shouldn't change the current behaviour for non-restricted namespaces.