Definitions
Policy as Code is a GitOps term for security, compliance, or release rules written as versioned machine-readable code. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Policy as Code before lunch, so the release did not sprint into production wearing untied shoes.”
Related Terms
- Admission PolicyGitOps and Release Engineering
Admission Policy is a GitOps term for a rule that evaluates resources before they are accepted by the cluster. It helps teams, humans, and agents compare declared source state with...
- Kyverno PolicyGitOps and Release Engineering
Kyverno Policy is a GitOps term for a Kubernetes-native policy rule for validating, mutating, or generating resources. It helps teams, humans, and agents compare declared source st...
- OPA GatekeeperGitOps and Release Engineering
OPA Gatekeeper is a GitOps term for a Kubernetes policy system often used to enforce admission constraints. It helps teams, humans, and agents compare declared source state with ru...
- Supply Chain PolicyGitOps and Release Engineering
Supply Chain Policy is a GitOps term for rules that decide which code, images, dependencies, and sources can be released. It helps teams, humans, and agents compare declared source...
- App of AppsGitOps and Release Engineering
App of Apps is a GitOps term for a GitOps pattern where one parent application manages child applications. It helps teams, humans, and agents compare declared source state with run...
- ApplicationSetGitOps and Release Engineering
ApplicationSet is a GitOps term for an Argo CD pattern for generating many related applications from a template. It helps teams, humans, and agents compare declared source state wi...