GitOps Overview
Deploy Pangolin and Sites (Newt) with GitOps workflows such as Argo CD or Flux.
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
What GitOps manages
A GitOps workflow can reconcile the same deployment inputs used by the other Kubernetes guides:
| Input | Used for |
|---|---|
| Helm chart values | Configure Pangolin, controller mode, database mode, ingress, Sites, and related components. |
| Kustomize overlays | Patch or compose rendered manifests for environment-specific deployments. |
| Kubernetes Secrets | Provide credentials, TLS material, database connection details, or Site connector credentials. |
| Custom resources | Manage Argo CD Applications, Flux HelmReleases, Flux Kustomizations, or related controller resources. |
Recommended layout
Keep the Pangolin and Site configuration close to the cluster or environment that owns it.
infrastructure/
├── clusters/
│ ├── production/
│ │ ├── pangolin/
│ │ └── sites/
│ ├── staging/
│ │ ├── pangolin/
│ │ └── sites/
│ └── dev/
│ ├── pangolin/
│ └── sites/
└── shared/
├── pangolin/
└── sites/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.