<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pod Security Standards :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/pod-security-standards/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/pod-security-standards/index.xml" rel="self" type="application/rss+xml"/><item><title>Pod Security Admission</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/pod-security-admission/index.html</link><pubDate>Tue, 27 Oct 2026 09:00:00 +0100</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/pod-security-admission/index.html</guid><description>Author: Fabrice JAMMES (LinkedIn).
Objective Apply the Pod Security Standards to a namespace with the Pod Security Admission controller:
Level Meaning privileged No restriction baseline Blocks the known privilege escalations: privileged, host namespaces, hostPath, extra capabilities… restricted Hardened pods: non-root user, allowPrivilegeEscalation: false, all capabilities dropped, seccomp profile Each level is applied in one or more modes, with a namespace label pod-security.kubernetes.io/&lt;mode&gt;=&lt;level&gt;:</description></item></channel></rss>