> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pangolin.net/llms.txt
> Use this file to discover all available pages before exploring further.

# GitOps Overview

> Deploy Pangolin and Sites (Newt) with GitOps workflows such as Argo CD or Flux.

<div id="pangolin-toc-cta" className="pangolin-toc-cta-source">
  <Card title="Try free on Pangolin Cloud" icon="cloud" href="https://app.pangolin.net/auth/signup" arrow="true" cta="Sign up free">
    Fastest way to get started with Pangolin using the hosted control plane. No credit card required.
  </Card>
</div>

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](/self-host/advanced/config-file) 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

<CardGroup cols={2}>
  <Card title="Argo CD Guide" href="/self-host/manual/kubernetes/gitops/argocd" icon="code-branch">
    Deploy Pangolin or Sites (Newt) with Argo CD Applications.
  </Card>

  <Card title="Flux Guide" href="/self-host/manual/kubernetes/gitops/flux" icon="code-branch">
    Deploy Pangolin or Sites (Newt) with Flux HelmRelease or Kustomization resources.
  </Card>
</CardGroup>

## 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.

```text theme={"theme":"gruvbox-light-hard"}
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.

## Next steps

<CardGroup cols={2}>
  <Card title="Argo CD Guide" href="/self-host/manual/kubernetes/gitops/argocd" icon="code-branch">
    Create Argo CD Applications for Pangolin and Sites (Newt).
  </Card>

  <Card title="Flux Guide" href="/self-host/manual/kubernetes/gitops/flux" icon="code-branch">
    Create Flux sources, HelmReleases, or Kustomizations for Pangolin and Sites (Newt).
  </Card>

  <Card title="Choose an Installation Path" href="/self-host/manual/kubernetes/choose-method" icon="route">
    Compare the supported Kubernetes deployment paths.
  </Card>

  <Card title="Prerequisites" href="/self-host/manual/kubernetes/prerequisites" icon="list-check">
    Review cluster, networking, storage, RBAC, and resource requirements.
  </Card>
</CardGroup>