#platform-architecture

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

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

Declarative Configuration is a GitOps term for configuration that describes the intended result instead of step-by-step commands. 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; Argo CD documentation.

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

Deployment Window is a GitOps term for an allowed time period for applying 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.

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

Desired State is a GitOps term for the declared configuration the system should converge toward. 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; Kubernetes controller pattern.

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

Drift Detection is a GitOps term for finding when live state differs from declared source state. 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 Drift Detection before lunch, so the release did not sprint into production wearing untied shoes.”

Drift Remediation is a GitOps term for the safe correction of detected drift back toward declared state. 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 Drift Remediation before lunch, so the release did not sprint into production wearing untied shoes.”

Emergency Patch is a GitOps term for a small urgent change applied to reduce active risk. 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 Emergency Patch before lunch, so the release did not sprint into production wearing untied shoes.”

Environment Branch is a GitOps term for a branch used to represent or promote a specific environment state. 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 Environment Branch before lunch, so the release did not sprint into production wearing untied shoes.”

Environment Lock is a GitOps term for a temporary lock that prevents changes to a target environment. 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 Environment Lock before lunch, so the release did not sprint into production wearing untied shoes.”

Environment Promotion is a GitOps term for moving a change from one environment to another with 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 Environment Promotion before lunch, so the release did not sprint into production wearing untied shoes.”

Ephemeral Environment is a GitOps term for a short-lived environment created for testing, review, or validation. 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 Ephemeral Environment 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.”

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

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

Flux Kustomization is a GitOps term for a Flux object that builds and applies manifests from a source. 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 Flux Kustomization before lunch, so the release did not sprint into production wearing untied shoes.”

Git Tag Promotion is a GitOps term for using a versioned Git tag to promote a release between 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 Git Tag Promotion before lunch, so the release did not sprint into production wearing untied shoes.”

GitOps is a GitOps term for using Git as the source of truth for declarative infrastructure and application operations. 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; Argo CD documentation; Flux documentation.

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

GitOps Controller is a GitOps term for software that observes source and live state, then reconciles resources safely. 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; Argo CD documentation; Flux documentation.

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

GitRepository Source is a GitOps term for a Flux source object that points to a Git 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: Flux documentation.

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

Health Check is a GitOps term for a public-safe signal that says whether an application or resource is usable. 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 Health Check before lunch, so the release did not sprint into production wearing untied shoes.”

Helm Chart is a GitOps term for a package format for Kubernetes resources and templates. 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 Helm Chart before lunch, so the release did not sprint into production wearing untied shoes.”