#devops

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

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

Owner Reference is a GitOps term for metadata linking a resource to the object that controls it. 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 Owner Reference 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.”

Work Queue is a GitOps term for the controller queue of resources waiting for reconciliation. 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 Work Queue 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.”

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

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

Kustomize Overlay is a GitOps term for a layer of patches and settings applied on top of a base manifest. 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 Kustomize Overlay 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.”

Overlay Patch is a GitOps term for a targeted change layered onto a base manifest. 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 Overlay Patch before lunch, so the release did not sprint into production wearing untied shoes.”