Skip to main content
Use GitOps when Pangolin and Sites (Newt) should be reconciled from Git instead of being installed manually from a local shell. Can be used together with Blueprints — see Blueprint config reference for details. These guides assume you already use, or plan to use, a GitOps controller such as Argo CD or Flux. General GitOps concepts such as reconciliation, desired state, and Git-driven workflows are outside the scope of this documentation. Refer to your GitOps controller’s documentation for those concepts.

​
Supported GitOps paths

Argo CD Guide

Deploy Pangolin or Sites (Newt) with Argo CD Applications.

Flux Guide

Deploy Pangolin or Sites (Newt) with Flux HelmRelease or Kustomization resources.

​
What GitOps manages

A GitOps workflow can reconcile the same deployment inputs used by the other Kubernetes guides: Keep the Pangolin and Site configuration close to the cluster or environment that owns it.
Use environment-specific directories for values, patches, and secrets that differ between clusters. Use shared directories only for reusable configuration that should stay the same across environments.

​
Next steps

Argo CD Guide

Create Argo CD Applications for Pangolin and Sites (Newt).

Flux Guide

Create Flux sources, HelmReleases, or Kustomizations for Pangolin and Sites (Newt).

Choose an Installation Path

Compare the supported Kubernetes deployment paths.

Prerequisites

Review cluster, networking, storage, RBAC, and resource requirements.