<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CEL :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/cel/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>Wed, 28 Oct 2026 09:00:00 +0100</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/cel/index.xml" rel="self" type="application/rss+xml"/><item><title>Allowed registries with a ValidatingAdmissionPolicy</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/allowed-registries/index.html</link><pubDate>Wed, 28 Oct 2026 09:00:00 +0100</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/allowed-registries/index.html</guid><description>Author: Fabrice JAMMES (LinkedIn).
Objective Only accept the pods whose images come from an allowed registry, with a ValidatingAdmissionPolicy: an admission rule written in CEL, run by the API server itself, without any webhook.
The CKS curriculum lists “Allowlist registries” in the Supply chain security domain. A ValidatingAdmissionPolicy (GA since Kubernetes 1.30) has two parts:
Object Role ValidatingAdmissionPolicy What is checked: the resources and the CEL expressions ValidatingAdmissionPolicyBinding Where and how: the namespaces, and the action (Deny, Warn, Audit) The lab works on a cluster shared by the trainees: the policy and its binding are cluster-wide objects, so their names end with your account, and the binding only applies to your namespace.</description></item></channel></rss>