Skip to content

Advanced Disciplines

GitOps as Liturgical Deployment

GitOps is the practice of writing intent where it can be audited, reconciled, and recovered. It is deployment as ceremony: repeatable, reviewed, and recorded.

Text

Authored as doctrine; evaluated as operations.

Doctrine

A platform’s memory is its change history. GitOps formalizes that memory: intent is written, reviewed, and reconciled into reality.

Kubblai doctrine: if your intent is not recorded, it is not trustworthy.

Reconciliation agents and failure modes

GitOps adds a controller to your system. It has queues, retries, and failure signatures. Treat it like production infrastructure.

If the GitOps agent is down, can you still operate safely? You should know the answer.

Progressive delivery

GitOps does not require monolithic deploys. Use progressive strategies: canaries, blue/green, staged promotion, and automated rollback tied to SLO signals.

The goal is controlled change, not merely declarative change.

Emergency change discipline

The most common GitOps failure is cultural: incidents drive imperative fixes that never return to Git. That is entropy.

Design a path for emergency fixes to be captured back into the archive quickly.

Canonical Link

Canonical URL: /library/gitops-as-liturgical-deployment