@platphorm_dictionary
Public approved definitions attributed to this handle. Private author metadata is not exposed.
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.”
OCIRepository Source is a GitOps term for a Flux source object that points to an OCI artifact 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 OCIRepository Source before lunch, so the release did not sprint into production wearing untied shoes.”
HelmRepository Source is a GitOps term for a Flux source object that points to Helm chart storage. 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 HelmRepository Source 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.”
HelmRelease is a GitOps term for a declarative Flux object for managing a Helm chart release. 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 HelmRelease before lunch, so the release did not sprint into production wearing untied shoes.”
ImagePolicy is a GitOps term for a Flux image automation rule that selects an image version. 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 ImagePolicy before lunch, so the release did not sprint into production wearing untied shoes.”
ImageUpdateAutomation is a GitOps term for a Flux workflow that writes selected image updates back to Git. 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 ImageUpdateAutomation before lunch, so the release did not sprint into production wearing untied shoes.”
Image Automation is a GitOps term for updating deployment source when an allowed image version is available. 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 Image Automation before lunch, so the release did not sprint into production wearing untied shoes.”
Semver Image Policy is a GitOps term for an image selection rule based on semantic version ranges. 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 Semver Image Policy before lunch, so the release did not sprint into production wearing untied shoes.”
Image Tag Drift is a GitOps term for a mismatch between the image tag in source and the running image evidence. 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 Image Tag Drift before lunch, so the release did not sprint into production wearing untied shoes.”
Immutable Artifact is a GitOps term for a build or package that should not change after publication. 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 Immutable Artifact before lunch, so the release did not sprint into production wearing untied shoes.”
Manifest Digest is a GitOps term for a content hash that identifies a specific manifest or 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 Manifest Digest before lunch, so the release did not sprint into production wearing untied shoes.”
Registry Mirror is a GitOps term for a trusted copy of image or artifact storage used for speed or resilience. 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 Registry Mirror before lunch, so the release did not sprint into production wearing untied shoes.”
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, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation; Kubernetes controller pattern.
“The team used Kubernetes Manifest before lunch, so the release did not sprint into production wearing untied shoes.”
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.”