OPA Policy Templating and Testing - Tejas Cherukara, ANZ Bank & Ben Ebsworth, Digio
summary
Shows how OPA policy becomes a production artifact: Rego is generated from templated Jinja policies with a shared library for common functions, unit tests are auto-generated and deliver 100% unit test coverage, and a small CLI (ankorCtl) plus CI pipelines run integration tests using kind-in-k8s to validate admission responses and mutations against a real cluster. Demo proves the pipeline runs end-to-end and catches policy regressions before merge.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:10OPA POLICY TEMPLATING AND TESTING
- 0:23What is OPA?
- 1:34USE CASE - DEV GUARDRAILS
- 2:23USE CASE - SECURITY
- 3:01USE CASE - ADMINISTRATIVE
- 3:59SIMPLIFIED EXTENSION & MAINTENANCE
- 5:36ADMISSION CONTROLLER
- 7:05PROVIDE AN ABSTRACTION CONSISTENT WITH EXISTING ECOSYSTEM (YAML)
- 8:34UNIT TESTING POLICY WITH 100% COVERAGE
- 9:37INTEGRATION TESTING
- 10:46ANCHORCTL
related talks
33mOpen Policy Agent Deep Dive
40mOPA Introduction & Community Update
41mOpen Policy Agent (OPA) Intro & Deep Dive
39mApplying Policy Throughout The Application Lifecycle with Open Policy Agent
45mOPA Deep Dive
32mOPA: So What Does the Policy Do?
39mOPA
31mDeploying Policy-as-Code with Readable Rego Policies, and Open Policy Agent
