feat(helm chart): add SecurityContext to pods and containers #917
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.
Speckle pods should run with minimal privileges and capabilities to function.
To verify, run the following and follow the advisory guidance:
helm template my-speckle-server ./utils/helm/speckle-server \ --values ../iain_speckle_dev-values.yaml \ --namespace speckle | \ docker run -i kubesec/kubesec:v2 scan /dev/stdin
Notes
seccompProfile
.seccompProfile
should be commented out while running kubesec 🙄emptyDir
) mounted at/tmp
for all containers that write temporary files. This allows root directory to be read only.NET_BIND_SERVICE
capability to run as nonRoot. ingress won't work without NET_BIND_SERVICE cap and allow-privilege-escalation for v0.20.0 or higer kubernetes/ingress-nginx#3668References
https://kubernetes.io/docs/concepts/security/pod-security-standards/
https://cheatsheetseries.owasp.org/cheatsheets/Kubernetes_Security_Cheat_Sheet.html
Fixes #857
Fixes #919