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
SOPS is a GitOps term for a file encryption workflow used to protect secrets in GitOps repositories. 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 SOPS before lunch, so the release did not sprint into production wearing untied shoes.”
Cluster Bootstrap is a GitOps term for the first GitOps setup that installs controllers and base configuration. 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 Cluster Bootstrap before lunch, so the release did not sprint into production wearing untied shoes.”
Bootstrap Repository is a GitOps term for the repository that contains the starting configuration for a cluster or fleet. 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 Bootstrap Repository before lunch, so the release did not sprint into production wearing untied shoes.”
Platform Repository is a GitOps term for a repository that stores shared platform services, policies, and add-ons. 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 Platform Repository before lunch, so the release did not sprint into production wearing untied shoes.”
Tenant Repository is a GitOps term for a repository where one team or tenant owns its application configuration. 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 Tenant Repository before lunch, so the release did not sprint into production wearing untied shoes.”
Infrastructure Repository is a GitOps term for a repository containing infrastructure definitions and 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 Infrastructure Repository before lunch, so the release did not sprint into production wearing untied shoes.”
Monorepo GitOps is a GitOps term for a GitOps layout where many services or environments live in one 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: OpenGitOps principles.
“The team used Monorepo GitOps before lunch, so the release did not sprint into production wearing untied shoes.”
Repo Per Environment is a GitOps term for a GitOps layout where each environment has its own repository boundary. 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 Repo Per Environment 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.”
Pull Request Gate is a GitOps term for a required review or check before source state can change. 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 Pull Request Gate before lunch, so the release did not sprint into production wearing untied shoes.”