GitOps
GitOps is an operational approach that uses version-controlled declarative configuration as the source of truth and automation to apply or reconcile system state.
Automating API Delivery
GitOps is an operational approach in which version-controlled Git repositories define desired system configuration and automated reconciliation applies it.
- How it is used
- Applies Git-based configuration changes to API gateway deployment while allowing developer self-service and operations review.
- How deep it goes
- Defines declarative, versioned, automatically pulled, and continuously reconciled configuration; identifies adoption challenges without detailing their tooling solutions.
- Examples
- Uses API gateway configuration, an environment repository, admin-UI drift, and git revert to illustrate deployment and rollback.
- What you can do after
- Operate/configure API gateway changes through reviewed Git PRs and automated reconciliation, while accounting for repository conflicts and secrets.
Platform Engineering on Kubernetes
GitOps is an operational model in which versioned declarative configuration is the source of truth and software agents automatically apply and reconcile it.
- How it is used
- Uses versioned environment configuration to deploy and promote service artifacts across running environments.
- How deep it goes
- Defines four principles and explains how automatic pulling and continuous reconciliation maintain desired state, without supplying implementation commands here.
- Examples
- Illustrates Git configuration changes reaching a Kubernetes cluster, with commit reverts for rollback and reuse across clusters.
- What you can do after
- Apply it via Argo CD to manage Kubernetes application environments from versioned configuration.
Read how Platform Engineering on Kubernetes explains GitOps →
Google Anthos in Action
GitOps is an operational model that manages system configuration and deployments declaratively from version-controlled repositories.
- How it is used
- Coordinates secure enterprise delivery by keeping infrastructure, platform, and application configuration in shared version-controlled interfaces.
- How deep it goes
- Explains repository responsibilities, manifest interfaces, cluster choices, and declarative synchronization, but stops short of detailing a complete implementation.
- Examples
- Uses a namespaced voting application, VirtualMachine manifests, multiple repositories, and cluster selectors for edge fleets.
- What you can do after
- Operate declarative deployments across Kubernetes clusters and stage releases by targeting selected clusters or namespaces.
Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu
A GitOps workflow is an infrastructure or deployment workflow in which Git repositories serve as the source of truth for declarative changes and automation applies those changes.
- How it is used
- Uses GitOps to make Git the source of truth for centralized Terraform infrastructure deployments instead of competing deployments from local machines.
- How deep it goes
- Defines four principles and explains drift reconciliation, while noting that Terraform alone cannot run it continuously.
- Examples
- Follows a developer from branch creation through tests, a speculative plan, review, merge, and deployment from main.
- What you can do after
- Practice/perform a branch-and-pull-request deployment workflow and use scheduled CD checks to detect drift.
Read how Terraform in Depth: Infrastructure as Code with Terraform and OpenTofu explains GitOps →
Kafka for Architects
A GitOps workflow manages infrastructure or application configuration declaratively through version-controlled files and automated reconciliation.
- How it is used
- Manages Kafka topics and infrastructure through version-controlled desired state, automated deployment, review, rollback, and drift detection.
- How deep it goes
- Explains declarative state, Git history, CI/CD reconciliation, rollback, and drift detection, but not low-level pipeline implementation.
- Examples
- Uses YAML or JSON Kafka definitions, pull-request review, drift validation, AsyncAPI generators, and a Customer 360 ODS deployment.
- What you can do after
- Operate/configure Kafka with reviewed, versioned desired state and automated synchronization between Git and the cluster.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
GitOps is an operational practice that manages infrastructure and application changes through version-controlled declarative definitions and automated reconciliation or deployment.
- How it is used
- Manages organization-wide infrastructure changes through code commits instead of manual tickets.
- How deep it goes
- Explains declarative configuration, drift detection, reconciliation, testing, and collaboration, without detailing controller internals.
- Examples
- Uses feature branches, pull requests, reviewers, automated tests, and Kubernetes controllers reconciling declarative configuration.
- What you can do after
- Apply it via version-controlled infrastructure commits, automated tests, and continuous reconciliation or deployment.
Related concepts
- gituses · Git is a distributed version-control system that records changes to files and supports managing project history and collaboration across repositories.
- versioninguses · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
- repositoryuses · A software repository is an organized storage location or collection of project files and related artifacts, often managed with version history and change tracking.
- reconciliationhas part · Reconciliation is the process of comparing related states, records, or outputs to identify differences and, when needed, resolve them or bring them into agreement.
- infrastructure as codeuses · Infrastructure as code is the practice of defining, provisioning, and managing computing infrastructure through machine-readable code or configuration rather than manual procedures.
- APIOpsused by · APIOps is the practice of automating the governance, delivery, and operation of API products across their life cycle.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.