#platform-architecture

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.”

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 running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used App of Apps before lunch, so the release did not sprint into production wearing untied shoes.”

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 with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used ApplicationSet before lunch, so the release did not sprint into production wearing untied shoes.”

Argo CD Application is a GitOps term for an Argo CD object that describes source, destination, and sync behavior for an app. 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.

“The team used Argo CD Application before lunch, so the release did not sprint into production wearing untied shoes.”

Audit Trail is a GitOps term for the recorded sequence of changes, approvals, and system actions. 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 Audit Trail before lunch, so the release did not sprint into production wearing untied shoes.”

Auto Sync is a GitOps term for a policy that lets the controller apply eligible changes automatically. 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.

“The team used Auto Sync before lunch, so the release did not sprint into production wearing untied shoes.”

Base Manifest is a GitOps term for the shared Kubernetes configuration used before environment-specific changes. 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 Base Manifest before lunch, so the release did not sprint into production wearing untied shoes.”

Blue Green Release is a GitOps term for a release strategy that switches between two complete environments. 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.

“The team used Blue Green Release before lunch, so the release did not sprint into production wearing untied shoes.”

Bootstrap Repository is a GitOps term for the repository that contains the starting configuration for a cluster or fleet. 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: Flux documentation.

“The team used Bootstrap Repository before lunch, so the release did not sprint into production wearing untied shoes.”

Branch Protection is a GitOps term for repository rules that prevent unsafe merges or unreviewed source changes. 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 Branch Protection before lunch, so the release did not sprint into production wearing untied shoes.”

Break Glass is a GitOps term for an emergency path for bypassing normal controls with clear evidence and review. 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 Break Glass before lunch, so the release did not sprint into production wearing untied shoes.”

Canary Release is a GitOps term for a release strategy that sends a small portion of traffic to a new version first. 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.

“The team used Canary Release before lunch, so the release did not sprint into production wearing untied shoes.”

Change Freeze is a GitOps term for a control window that limits changes during high-risk times. 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 Change Freeze before lunch, so the release did not sprint into production wearing untied shoes.”

Chart Values is a GitOps term for configuration inputs supplied to a Helm chart. 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 Chart Values before lunch, so the release did not sprint into production wearing untied shoes.”

ChatOps Approval is a GitOps term for an approval or action requested through a team chat workflow. 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 ChatOps Approval before lunch, so the release did not sprint into production wearing untied shoes.”

Cluster Bootstrap is a GitOps term for the first GitOps setup that installs controllers and base configuration. 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 Cluster Bootstrap before lunch, so the release did not sprint into production wearing untied shoes.”

Commit Provenance is a GitOps term for evidence about who created a commit, when it happened, and what it changed. 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 Commit Provenance before lunch, so the release did not sprint into production wearing untied shoes.”

Commit SHA Pinning is a GitOps term for locking deployment source to a precise Git commit identifier. 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.

“The team used Commit SHA Pinning before lunch, so the release did not sprint into production wearing untied shoes.”

Controller Runtime is a GitOps term for the libraries and patterns used to build Kubernetes controllers. 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 Controller Runtime before lunch, so the release did not sprint into production wearing untied shoes.”

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 systems, then act without pretending a deployment did more than the evidence shows. Source context: Kubernetes controller pattern.

“The team used CRD before lunch, so the release did not sprint into production wearing untied shoes.”