Skip to content

SYSTEM Cited by 2 sources

Open Policy Agent (OPA / Gatekeeper)

Open Policy Agent (OPA) is a CNCF-graduated general-purpose policy engine; Gatekeeper is the Kubernetes admission-controller integration built on top of it. Policies are written in Rego, a declarative logic-programming language, and evaluated against structured input (Kubernetes API requests, application requests, CI/CD metadata, …).

In the Kubernetes deployment model, Gatekeeper enforces policies on every CREATE / UPDATE admission — the cluster API server calls into Gatekeeper, Gatekeeper evaluates the policy set against the incoming object + live state, and either admits or rejects. This is patterns/policy-gate-on-provisioning in wiki terms: compliance at manifest-submission time, shift-left from post-hoc audit.

OPA's place in the policy-engine landscape

OPA / Rego vs Cedar / AVP vs AWS SCPs — three different policy engines, three slightly different niches:

Engine Language Primary enforcement layer Analyzability by design?
OPA / Gatekeeper Rego (Datalog-ish) K8s admission; also app auth Partial (general-purpose)
Cedar / AVP Cedar App-request time Yes (constrained-by-design)
AWS SCPs IAM policy JSON AWS Organizations (account-wide) Yes (SMT-proven via systems/aws-policy-interpreter)

All three are concepts/policy-as-data instances — policies in a store separate from code, versioned, audited.

Seen in

Stub page — OPA internals (Rego semantics, partial evaluation, constraint templates, Gatekeeper mutation, bundle distribution) out of scope until a future source drills into them.

Last updated · 200 distilled / 1,178 read