GitOps
GitOps combines a versioned desired state with automatic retrieval and continuous reconciliation. Configuration files in Git alone cover only part of this process.
What is GitOps?
GitOps is an operating approach in which the desired system state is described declaratively and stored with an immutable version history. Software agents automatically retrieve these descriptions and continuously reconcile the actual state with them. These are the core principles of OpenGitOps. A repository without this continuous reconciliation covers only part of the approach.
Example: reconciling the portal version
In this fictional example, a reviewed configuration specifies which container image a customer portal should use. An agent reads the approved version and attempts to bring the running environment into line. The team can track differences and failed changes. Failed reconciliation must remain visible so the team can intervene.
The approved source, the agent’s access rights and error handling must be clear. A stored desired state does not prove that it has been successfully applied.
Returning to an earlier configuration can request an earlier software version. It does not reverse changes made to business data in the meantime. Before taking this step, the application must be compatible with the current data; restoring data remains a separate task.
Sources
Related terms
- Infrastructure as CodeInfrastructure as Code describes infrastructure in files that can be versioned and reviewed. Managed resources only change when those changes are actually applied.
- DockerDocker provides tools to build, distribute and run containerised applications. The image, running container and operating environment serve different purposes.
- Container registryA container registry stores and distributes images. Tags can change; a digest identifies content but does not establish approval of the software version.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support