Kubernetes simcore: add pod security standard #1139
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
Ensure baseline policy and warn on restricted policy violations. The k8s way to add pod security standard, is to add labels to the namespace. The adding labels to namespace is achieved via helmfile hooks. Add helpful defaults for pod & container security context to ensure minimal privileges. WARNING: if deployed pod does not conform with baseline policy, it SILENTLY won't be scheduled. To see warnings / errors execute `kubectl -n simcore events' * ITISFoundation#1137
sanderegg
approved these changes
Jul 21, 2025
mrnicegyu11
reviewed
Jul 21, 2025
mrnicegyu11
approved these changes
Jul 21, 2025
Member
mrnicegyu11
left a comment
mrnicegyu11
left a comment
There was a problem hiding this comment.
very cool, excited to see this! 🌋
YuryHrytsuk
deleted the
kubernetes-simcore-charts-default-pod-security-context
branch
YuryHrytsuk
added a commit
to YuryHrytsuk/osparc-ops-environments
that referenced
this pull request
Jul 21, 2025
In ITISFoundation#1139 resource usage tracker (RUT) chart dependencies were updated but no Chart.lock was not. This PRs updates Chart.lock (via helm dependency update). Bonus: * Automate this with pre-commit hook * fixes bug from ITISFoundation#1139
1 task
YuryHrytsuk
added a commit
that referenced
this pull request
Jul 21, 2025
* Kubernetes: update Chart.lock of RUT In #1139 resource usage tracker (RUT) chart dependencies were updated but no Chart.lock was not. This PRs updates Chart.lock (via helm dependency update). Bonus: * Automate this with pre-commit hook * fixes bug from #1139 * Remove readme (it is automated now) * Improve pre-commit hook
88 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 do these changes do?
Ensure baseline policy and warn on restricted policy violations. The k8s way to add pod security standard, is to add labels to the namespace. The adding labels to namespace is achieved via helmfile hooks. This policy forces pod to define some security settings (e.g.
privileged: false). Read more https://kubernetes.io/docs/concepts/security/pod-security-standards/WARNING: if deployed pod does not conform with baseline policy, it SILENTLY won't be scheduled. To see warnings / errors execute `kubectl -n simcore events'
Add helpful defaults for pod & container security context to ensure minimal privileges.
FYI: @pcrespov
Related issue/s
Related PR/s
Checklist