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

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# GitOps Delivery

> Use Git repositories as the source of truth for automated app delivery to edge Kubernetes clusters.

GitOps is a delivery model that uses a Git repository as the source of truth for application state. ZEDEDA Edge Kubernetes Service includes a built-in GitOps engine based on the Rancher Fleet format. When a GitOps repository is connected to the service, the agent monitors the repository every 60 seconds and automatically applies changes to the target clusters. After initial setup, you do not need to perform manual deployment steps.

## How GitOps Delivery Works

GitOps delivery follows this sequence:

1. Register a Git repository under **Infrastructure > Operations > GitOps Repos**.
2. Specify the target clusters that should receive deployments from the repository. Choose **All Clusters** or an individual cluster. Only clusters that run Kubernetes are listed. When selecting an individual cluster, hover over a cluster name in the list until a checkbox appears, then select it.
3. The GitOps agent polls the repository and deploys changes to the target clusters automatically.
4. Optionally, include a `fleet.yaml` file in the repository to customize per-cluster deployment behavior, such as value overrides or cluster exclusions.

## Next Steps

> [card] [Create GitOps Repositories](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/create-gitops-repositories.md)
>
> Connect a Git repository to ZEDEDA Edge Kubernetes Service and configure authentication, targets, and sync settings.

> [card] [GitOps fleet.yaml Examples](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/gitops-fleet-yaml-examples.md)
>
> Customize Helm chart deployments across clusters with fleet.yaml configuration examples.

> [card] [Manage Cluster Groupings](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/manage-kubernetes-cluster-groupings.md)
>
> Organize clusters into groups to view and manage them as a single unit.

> [card] [Edge Kubernetes Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/edge-kubernetes-operations.md)
>
> Overview of ZEDEDA Edge Kubernetes Service operations and capabilities.