Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
1,322 definitions
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.”
Self-Heal is a GitOps term for automatic correction when live state drifts away from 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.
“The team used Self-Heal before lunch, so the release did not sprint into production wearing untied shoes.”
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 systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Prune before lunch, so the release did not sprint into production wearing untied shoes.”
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 with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Orphaned Resource before lunch, so the release did not sprint into production wearing untied shoes.”
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.”
Rollback is a GitOps term for returning to a previous known configuration or artifact 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: Argo CD documentation.
“The team used Rollback before lunch, so the release did not sprint into production wearing untied shoes.”
Roll Forward is a GitOps term for fixing an issue by moving to a newer corrected version instead of going backward. 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 Roll Forward 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.”
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.”
Promotion PR is a GitOps term for a pull request that moves a known change into the next 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 Promotion PR before lunch, so the release did not sprint into production wearing untied shoes.”