Skip to main content
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

Create GitOps Repositories

Connect a Git repository to ZEDEDA Edge Kubernetes Service and configure authentication, targets, and sync settings.

GitOps fleet.yaml Examples

Customize Helm chart deployments across clusters with fleet.yaml configuration examples.

Manage Cluster Groupings

Organize clusters into groups to view and manage them as a single unit.

Edge Kubernetes Overview

Overview of ZEDEDA Edge Kubernetes Service operations and capabilities.