🌱 Update deployment to follow best practices #241
Merged
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
|
avorima
force-pushed
the
security-manifest
branch
from
176623c to
f93ba02
Compare
|
avorima
requested review from
gfariasalves-ionos,
jriedel-ionos,
mcbenjemaa,
piepmatz and
wikkyk
as code owners
piepmatz
reviewed
Feb 12, 2025
piepmatz
approved these changes
Feb 13, 2025
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.
What is the purpose of this pull request/Why do we need it?
Allow deploying the provider in a restricted namespace.
Issue #, if available:
Description of changes:
Add required fields to pod and container security context.
Special notes for your reviewer:
https://kubernetes.io/docs/concepts/security/pod-security-standards/
Checklist: