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.”
Related Terms
- External SecretsGitOps and Release Engineering
External Secrets is a GitOps term for a pattern that syncs secrets from a protected external store into the runtime. It helps teams, humans, and agents compare declared source stat...
- Sealed SecretsGitOps and Release Engineering
Sealed Secrets is a GitOps term for encrypted Kubernetes secrets that a controller can decrypt inside the cluster. It helps teams, humans, and agents compare declared source state ...
- Secret SealingGitOps and Release Engineering
Secret Sealing is a GitOps term for encrypting a secret so it can be safely stored in a repository. It helps teams, humans, and agents compare declared source state with running sy...
- Break GlassGitOps and Release Engineering
Break Glass is a GitOps term for an emergency path for bypassing normal controls with clear evidence and review. It helps teams, humans, and agents compare declared source state wi...
- Signed CommitGitOps and Release Engineering
Signed Commit is a GitOps term for a Git commit with cryptographic proof of author or system identity. It helps teams, humans, and agents compare declared source state with running...
- Signed ImageGitOps and Release Engineering
Signed Image is a GitOps term for a container image with cryptographic proof attached to the artifact. It helps teams, humans, and agents compare declared source state with running...