Securing the Kubernetes Empire with OpenPolicyAgent and Rego
summary
Explains how OpenPolicyAgent + Rego run as a service or library and how OPA Gatekeeper enforces Kubernetes policies via internal registries only and CRD-based constraint templates, with examples for JWT decoding, a failing pod blocked for missing team label, running as root, or exceeding a 200m CPU limit. Shows Helm/kubectl install (two commands), audit vs deny modes, scaling replicas, and a prebuilt Gatekeeper library; recommends KISS, deny-by-default, and keeping all policies in Git for reproducible, auditable enforcement.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:46Agenda
- 3:54Policy as code in Kubernetes
- 10:13OPA and Rego basics
- 14:23OPA in Kubernetes with Gatekeeper
- 17:13Policy enforcement with constraints
- 21:54Live demo: Gatekeeper policies
- 24:21Gatekeeper library and community
- 25:03Best practices for Rego policies
- 28:35Future of policy management
- 30:00Q&A
related talks
39mApplying Policy Throughout The Application Lifecycle with Open Policy Agent
25mPolicing Your Kubernetes Clusters with Open Policy Agent (OPA) - Mark Puddick & Amith Nambiar
32mSecuring our clusters with gatekeeper and OPA
14mPolicy-as-code for Kubernetes with Gatekeeper
25mPolicing Your Kubernetes Clusters with Open Policy Agent (OPA)
30mOpen Policy Agent Intro
35mEnforcing Service Mesh Structure using OPA Gatekeeper
28mEmbracing change: Policy-as-code for Kubernetes with OPA and Gatekeeper
