What Really Happens After SCC Admission in OpenShift?
The article discusses the intricacies of Security Context Constraints (SCC) in OpenShift and their role in managing container capabilities. It highlights a scenario where a development team encounters issues with ICMP ping health checks despite the SCC allowing the necessary capabilities. The author emphasizes that SCCs are admission-time gates and do not enforce runtime privileges, which can lead to misunderstandings among engineers.
- ▪Security Context Constraints (SCC) control the security configuration allowed in OpenShift clusters.
- ▪SCCs do not enforce runtime privileges; they only determine if a security configuration can be submitted.
- ▪The actual enforcement of capabilities occurs in a separate stack involving kubelet, CRI-O, and the Linux kernel.
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/nhegde/what-really-happens-after-scc-admission-in-openshift-3hin |
| Publication time | Thu, 21 May 2026 07:11:25 +0000 |
| Retrieval time | 2026-05-21T07:35:03.553Z |
| Last seen | 2026-05-21T07:35:03.553Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cSv0NdqBtjZX |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3943457) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Nandan Hegde Posted on May 21 What Really Happens After SCC Admission in OpenShift? #kubernetes #linux #openshift #security A Debugging Story That Will Change How You Think About Container Capabilities You are a platform engineer running OpenShift. A development team runs a monitoring sidecar as a non-root user that needs to perform ICMP ping health checks. They need CAP_NET_RAW - the capability required for raw socket access. Straightforward enough.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
