Design Patterns for OPA and Cloud Native Authorization
summary
Open Policy Agent (OPA) and its Rego policy language provide concrete patterns: run OPA offline on developer laptops and CI to block bad configs (seconds–minutes acceptable), run OPA as an admission hook for live Kubernetes with ~10–100 ms latency, or deploy a sidecar per instance for API auth with ~1 ms targets and ~1k QPS. Policies use JSON inputs, external data like PagerDuty or LDAP for context, and operational choices include fail open vs fail closed and centralized vs replicated deployment.
AI-written summary · about
chapters (7)
- 0:00Start
- 8:31What Is Oppa
- 11:23Data and Json
- 15:07Policy Language
- 25:48Opus Policy Language
- 29:13Online Version of Configuration Authorization
- 35:41Policies
related talks
38mOPA for the cloud natives
19mDynamic Authorization and Policy Control for Your Kubernetes Cluster
36mOPA for the cloud natives
34mFine-grained Authorization in a Containerized World
33mOpen Policy Agent Deep Dive
45mOpen Policy Agent Deep Dive
38mPolicy as Code with Open Policy Agent
41mOpen Policy Agent (OPA) Intro & Deep Dive
