k8s Validating Admission Policy And Crossplane - Viktor Farcic
summary
Claim: enforce Policy-as-Code for an Internal Developer Platform by validating a single high-level resource instead of dozens of low-level objects. Uses Crossplane plus Kubernetes Validating Admission Policy (alpha/beta); examples include an admission rule to limit deployments to 5 replicas and a custom SQLClaim resource that expands into many primitives. Notes concrete scale: cluster exposes 180 CRDs and a single SQLClaim spawns multiple AWS objects via Crossplane. Demo shows policy authoring and binding but the validating policy fails in the demo due to alpha spec changes.
AI-written summary · about
chapters (10)
- 0:00Introduction and disclaimer
- 0:42Kubernetes admission controllers explained
- 3:31Validating admission policies overview
- 7:02Challenges with Kubernetes policies
- 10:37Crossplane and CRDs for simplification
- 14:33Demo with Crossplane SQL claim
- 17:25Policy creation for SQL claim
- 21:42Testing and limitations of alpha features
- 24:16Future of validating admission policies
- 24:58Q&A session
related talks
34mHow To Fight Misconfiguration And Bad Intentions
35mBuilding and Enabling APIs with Crossplane 1
30mA Practical Guide To Kubernetes Policy as Code
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
27mPolicy-Based Infrastructure as Code with Kyverno
26mPolicy as Code: Past, Present and Future for Novice
37mPlatformOps with Crossplane
33mEliminating the Gap Between Development and Production with Kuber...