- Notifications
You must be signed in to change notification settings - Fork7
feat: Add ability to define securityContext#99
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
feat: Add ability to define securityContext#99
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Signed-off-by: Marco Maurer <mkilchhofer@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
mkilchhofer commentedMay 6, 2025
May I have your attention@mafredri@ericpaulsen ? |
ericpaulsen left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
I'd like to define a securityContext to harden the deployment as much as possible.
Setting the securityContext is already possible for the
coderhelm chart but sadly not for the logstream component :)