Policy as [versioned] Code
summary
Claims that policy becomes a maintainable artifact: put policy in a GitHub repo, semantic versioning it, ship tests, and treat it as a dependency so apps get automated PRs via Renovate. Prototype uses Terraform and Kubernetes with chekkov for Terraform checks and canervo for Kubernetes, tags like 1.00 → 2.00 → 2.1.1, and a small bash shim to run local/CI evaluations. Runtime enforcement uses Kubernetes admission controllers; the proof‑of‑concept works but needs cleaner tooling and cloud vendor integration.
AI-written summary · about
chapters (9)
- 0:00Policy pain
- 6:08Introduction
- 7:55Policy as code goals
- 11:47Why policy as code fails
- 16:40Policy as dependency
- 17:00Live demo
- 21:38Policy context
- 23:22Cultural shift
- 24:06Purposeful policy
related talks
23mPolicy as [versioned] Code
22mPolicy as [versioned] Code - How to do it Right
34mPolicy As [Versioned] Code
10mLightning Talk: Policy as [Versioned] Code - You're Doing It Wrong.
12mEnd-to-end policy-as-code from IaC to Running Workloads
41mModern Policy Management Putting responsibility where it belongs
32mCloud Native Policy as Code: Principles and Best Practices
30mA Practical Guide To Kubernetes Policy as Code
