liveBook · Manning

Argo

As explained in Effective Platform Engineering

Argo CD is a Kubernetes continuous-delivery tool that synchronizes applications with declarative configuration stored in version control.

Argo CD is a Kubernetes continuous-delivery tool that synchronizes applications with declarative configuration stored in version control. It separates deployment execution from pipeline orchestration. section 8.2.1

Argo supports platform delivery by:

  • Deploying Helm- or Kustomize-generated resources without giving pipelines direct Kubernetes API access. section 8.2.1
  • Letting developers control deployment timing, versions, and testing through the primary pipeline orchestration tool. section 8.2.1
  • Operating centrally across clusters or running as part of individual cluster definitions. section 8.2.1

Centralized multi-cluster deployment

A platform can provide one centralized Argo instance that manages deployments across every cluster in a release pipeline. At scale, performance concerns may motivate running a deployer with each cluster. section 8.2.1

How Effective Platform Engineering covers it

How deep it goes
Explains deployment responsibilities and centralized versus per-cluster placement, but defers detailed scaling strategies.
Examples
Uses centralized multi-cluster management and per-cluster deployment as contrasting operating models.
What it assumes
Assumes Kubernetes, release pipelines, and generated deployment resources; does not establish those concepts from zero.
What you can do after
Operate Kubernetes deployments through a dedicated deployer without granting pipelines direct Kubernetes API access.
How it connects
Connects Kubernetes deployments with Helm, Kustomize, pipeline orchestration, Flux, and secrets management.

Also explained in

Compare how 4 books explain Argo →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.