<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security Context :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/security-context/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>Tue, 27 Oct 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/security-context/index.xml" rel="self" type="application/rss+xml"/><item><title>Security context</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/security-context/index.html</link><pubDate>Tue, 27 Oct 2026 09:00:00 +0100</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/security-context/index.html</guid><description>Author: Fabrice JAMMES (LinkedIn).
Objective Use the securityContext of a pod and of its containers to control the user, the Linux capabilities and the filesystem access of the processes, and understand the risks of the host namespaces.
The lab works on a cluster shared by the trainees: each one works in a namespace of their own. On OpenShift, the SCCs reject or modify most of these pods: compare with the SCC lab.</description></item></channel></rss>