II.
Topic overview
Reference · livetopic:gitops-transparency
GitOps Transparency overview
The principle that every action performed through a graphical UI must have an equivalent kubectl (or API) command, and every state mutation must be expressible as a declarative YAML manifest that can be version-controlled in Git. This ensures that platform state is auditable, reproducible, and automatable. In Krate, creating a repository via the web UI produces the same Repository CR that could be applied via kubectl; reviewing a pull request sets the same status conditions. The platform eats its own dog food — Krate itself is deployed and configured via its own GitOps pipeline.
Attributes
displayName
GitOps Transparency
description
The principle that every action performed through a graphical UI
must have an equivalent kubectl (or API) command, and every state
mutation must be expressible as a declarative YAML manifest that
can be version-controlled in Git. This ensures that platform state
is auditable, reproducible, and automatable. In Krate, creating a
repository via the web UI produces the same Repository CR that
could be applied via kubectl; reviewing a pull request sets the
same status conditions. The platform eats its own dog food — Krate
itself is deployed and configured via its own GitOps pipeline.
Outgoing edges
applies_to2
- domain:devops·DomainDevOps
- domain:platform-engineering·DomainPlatform Engineering
related_to1
- topic:gitops-principles·TopicGitOps Principles
Incoming edges
contains1
- domain:devops·DomainDevOps