Definitions
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 state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Kubernetes controller pattern.
“The team used Kyverno Policy 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...
- 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...
- CRDGitOps and Release Engineering
CRD is a GitOps term for a CustomResourceDefinition that teaches Kubernetes about a new resource type. It helps teams, humans, and agents compare declared source state with running...
- Custom ResourceGitOps and Release Engineering
Custom Resource is a GitOps term for a Kubernetes API extension managed by controllers. It helps teams, humans, and agents compare declared source state with running systems, then ...
- FinalizerGitOps and Release Engineering
Finalizer is a GitOps term for metadata that lets a controller clean up before deletion finishes. It helps teams, humans, and agents compare declared source state with running syst...
- Kubernetes ManifestGitOps and Release Engineering
Kubernetes Manifest is a GitOps term for YAML or JSON that declares Kubernetes resource state. It helps teams, humans, and agents compare declared source state with running systems...