Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
1,322 definitions
Signed Image is a GitOps term for a container image with cryptographic proof attached to the artifact. 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 Signed Image before lunch, so the release did not sprint into production wearing untied shoes.”
SBOM Gate is a GitOps term for a release check that requires software bill of materials evidence before promotion. 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 SBOM Gate before lunch, so the release did not sprint into production wearing untied shoes.”
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 state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.
“The team used Supply Chain Policy before lunch, so the release did not sprint into production wearing untied shoes.”
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.”
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 running systems, then act without pretending a deployment did more than the evidence shows. Source context: Kubernetes controller pattern.
“The team used Admission Policy before lunch, so the release did not sprint into production wearing untied shoes.”
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 running systems, then act without pretending a deployment did more than the evidence shows. Source context: Kubernetes controller pattern.
“The team used OPA Gatekeeper before lunch, so the release did not sprint into production wearing untied shoes.”
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.”
Secret Sealing is a GitOps term for encrypting a secret so it can be safely stored in a repository. 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: Argo CD documentation; Flux documentation.
“The team used Secret Sealing before lunch, so the release did not sprint into production wearing untied shoes.”
Sealed Secrets is a GitOps term for encrypted Kubernetes secrets that a controller can decrypt inside the cluster. 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: Argo CD documentation; Flux documentation.
“The team used Sealed Secrets before lunch, so the release did not sprint into production wearing untied shoes.”
External Secrets is a GitOps term for a pattern that syncs secrets from a protected external store into the runtime. 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: Argo CD documentation; Flux documentation.
“The team used External Secrets before lunch, so the release did not sprint into production wearing untied shoes.”