Menu

OpenShift SecurityContextConstraints: why your upstream Helm chart refuses to start
πŸ“°

OpenShift SecurityContextConstraints: why your upstream Helm chart refuses to start

DEV Community: kubernetesΒ·Florient DOGBEΒ·7 days ago
#oXsXXJro
#devtokubernetes#devto#dev#myapp#openshift
Reading 0:00
15s threshold

You helm install a popular chart that works perfectly on EKS, GKE or a kind cluster. On OpenShift, the Deployment is created, the ReplicaSet is created... and no Pod ever appears. Or the Pod appears and crashloops with Permission denied on a directory it just tried to write to.

Welcome to SecurityContextConstraints (SCC). This article walks through the admission mechanics, how to diagnose exactly which SCC was applied (or refused), how to adapt an upstream chart without forking it, and β€” when there is no other option β€” how to create a narrowly scoped custom SCC instead of handing out anyuid to everyone.

Context: why public charts break on OpenShift

Most community charts are written against a permissive baseline.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.