GitOps

As explained in Google Anthos in Action

GitOps is an operational model that manages system configuration and deployments declaratively from version-controlled repositories.

GitOps is an operational model in which system configuration and deployments are described declaratively in version-controlled repositories. Separate teams maintain configuration sets, while shared interfaces connect repositories, image builds, Kubernetes manifests, and delivery workflows. section 12.6 section 8.3.2

A GitOps implementation assigns responsibility across several operational boundaries:

• Store infrastructure, platform, and application definitions as configuration files in version control. section 12.6
• Use Kubernetes manifests as a common interface between development, operations, security, and delivery responsibilities. section 12.6
• Apply manifests declaratively and asynchronously, including manifests defining VirtualMachine custom resources. section 8.3.2
• Choose a single cluster with multiple namespaces for single-site or nonproduction setups, or multiple clusters for high availability, global latency, and staged rollout needs. section 12.6

Multi-cluster application delivery

A microservices voting system runs on an Anthos GKE cluster with separate Voting, Transfer, and Results namespaces. For broader availability or lower rollout impact, multiple clusters can receive the application incrementally before full release. section 12.6

Figure 12.46 Application delivery workflow

Use the application delivery workflow to trace how repositories, builds, manifests, and deployment targets connect. section 12.6

Figure 8.7 Anthos Config Management with multiple repositories

Use the multiple-repository diagram to examine how Anthos Config Management synchronizes configuration across a cluster fleet. section 8.3.2

How Google Anthos in Action covers it

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 it assumes

Assumes Kubernetes orchestration, microservices, repositories, image builds, and manifest definitions as established delivery components.

What you can do after

Operate declarative deployments across Kubernetes clusters and stage releases by targeting selected clusters or namespaces.

How it connects

Connects version control, CI/CD, Kubernetes, microservices, Anthos Config Management, multicluster deployment, and declarative management.

liveBookmanning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Automating API DeliveryGitOps is an operational approach in which version-controlled Git repositories define desired system configuration and automated reconciliation applies it.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesGitOps is an operational model in which versioned declarative configuration is the source of truth and software agents automatically apply and reconcile it.
• 

  liveBookmanning.com
  Terraform in Depth: Infrastructure as Code with Terraform and OpenTofuA 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.
• 

  liveBookmanning.com
  Kafka for ArchitectsA GitOps workflow manages infrastructure or application configuration declaratively through version-controlled files and automated reconciliation.
• 

  liveBookmanning.com
  Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformGitOps is an operational practice that manages infrastructure and application changes through version-controlled declarative definitions and automated reconciliation or deployment.

Compare how 6 books explain GitOps →

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.

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.