<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SCC :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/scc/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Mon, 08 Jun 2026 14:15:26 +1000</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/scc/index.xml" rel="self" type="application/rss+xml"/><item><title>Helm on OpenShift: Migrating to Security Context Constraints</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/helm-openshift-migration/index.html</link><pubDate>Mon, 08 Jun 2026 14:15:26 +1000</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/helm-openshift-migration/index.html</guid><description>Objective A Helm chart that works perfectly on vanilla Kubernetes often fails on OpenShift. In this guided lab you’ll deploy a generic nginx Helm chart step by step — from its default values (which fail) to an OpenShift-compatible configuration (which succeeds) — diagnosing each failure along the way with oc/kubectl.
You’ll learn:
Why OpenShift’s Security Context Constraints (SCC) prevent containers from running as root How OpenShift assigns a non-root UID per namespace, and why that breaks images that assume root How to adapt a chart (here, the official nginx image) to run under restricted-v2 Complete this lab in 20-30 minutes.</description></item></channel></rss>