Definitions
Resource Pruning is a GitOps term for the controlled deletion of unmanaged or removed resources during sync. 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 Resource Pruning before lunch, so the release did not sprint into production wearing untied shoes.”
Related Terms
- Orphaned ResourceGitOps and Release Engineering
Orphaned Resource is a GitOps term for a live object that is not clearly owned by the current desired source state. It helps teams, humans, and agents compare declared source state...
- PruneGitOps and Release Engineering
Prune is a GitOps term for removing live resources that are no longer present in desired source state. It helps teams, humans, and agents compare declared source state with running...
- Admission PolicyGitOps and Release Engineering
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...
- App of AppsGitOps and Release Engineering
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 run...
- ApplicationSetGitOps and Release Engineering
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 wi...
- Argo CD ApplicationGitOps and Release Engineering
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 sou...