Create ZEDEDA Edge Kubernetes App Flows GitOps Repositories Using the GUI

Updated January 06, 2026 20:05

Introduction

Add GitOps Repositories to use GitOps for app management. If you store application configurations (sometimes known as a helm chart or manifest) in GitOps Repositories, you can monitor the Git repo for any changes. After a change is detected, the state is pulled from Git into the cluster and activated.

Note that this is not the same as a ZEDEDA Edge Kubernetes App Flows Marketplace App Repository. A GitOps repository is strictly for GitOps and an App Repository is strictly for a Kubernetes Flows Marketplace App. These two repository types are for mutually exclusive purposes. Helm charts in GitOps Repositories must have the values explicitly defined (fully rendered) whereas Helm charts in a Kubernetes Marketplace App Repository can have values undefined (templates).

This is a series of articles. You will likely follow them in this order.

Prerequisites

You have onboarded one or more edge nodes.
Your edge nodes are online.
Your edge nodes are running the EVE-k v16.0.0 or greater (EVE-OS KVM is not supported).
For installation, we recommend all the edge nodes be of the same hardware type/model with a minimum of 12 core CPUs, 16 GB RAM, and NVMe SSDs for EVE persistent storage for optimal performance.
For runtime, EVE-k consumes approximately 4 GB of memory and 2 vCPUs if used for clustering.
It recommended, though not strictly required, to separate the management traffic from the cluster traffic.
You have already created a ZEDEDA Edge Kubernetes Service Cluster.
You already have helm charts in a GitOps Repository.
You have either the SysManager or SysAdmin role in your ZEDEDA Cloud enterprise.

Add a ZEDEDA Edge Kubernetes App Flows GitOps Repositories

You cannot add an edge node to a cluster if an application instance is running on it.

Click on Edge Kubernetes > GitOps Repositories in the left panel.
Click + at the top right of the page to add a repository.
Enter the Git repo Name.
This is unique across the enterprise and cannot be changed.
Enter the Title.
This value is not used by the ZEDEDA Cloud system. It’s offered to give you more flexibility in organizing your enterprise. It can be changed after you create the object.
Select the same Project from the drop-down that your Edge Kubernetes Cluster belongs to.
Enter a Description to help other admins understand the purpose of the cluster or any important details.
Continue on to the configuration sections as needed, such as configure the Edge Kubernetes Git Repo Source.
Click Create when finished.

Configure the ZEDEDA Edge Kubernetes App Flows Git Repo Source

Enter your GitOps Repository URL.
- HTTPS: https://git.com
- SSH: ssh://user@host:port/owner/<repo-name>.git
Select to Watch for changes to the repo by either:
- A Branch - pinned to the HEAD of a specific branch.
- A Revision - pinned to a specific commit, tag, or version. Note that if you pick a tag that changes such as latest, that can automatically trigger the activation.
Enter the Branch Name or the specific commit.
Select the Git Authentication:
- Create a HTTP Basic Auth Secret with Username and Password - For use if your Git repository is accessed via HTTPS, with a management password that’s separate from your user password.
- Create a SSH Key Secret with Public Key and Private Key - Note that the private key must be unencrypted; passphrase-protected keys are not supported.
- None - For use only if your Git repository is publicly accessible and contains no sensitive information.
Enter the Path to the directory inside your repository that contains the manifests you want to deploy.
- Click the + to add more paths if you have more than one directory.
If you’re using a Git repo, select Git Authentication from the drop-down or click Add Secret to add authentication details manually:
- Create a HTTP Basic Auth Secret with Secret Name, Username, and Password.
- Create a SSH Key Secret with Public Key and Private Key - Note that the private key must be unencrypted; passphrase-protected keys are not supported.
If you’re using a non-Git repo, select the Helm Authentication from the drop-down or click Add Secret to add authentication details manually:
- Create a HTTP Basic Auth Secret with Username, Password, and Helm Repo (URL Regex).
- Create a SSH Key Secret with Public Key, Private Key, and Helm Repo (URL Regex).
- None
Select a TLS Certificate Verification.
- A Valid Certificate
- Specify Additional Certificate if you have a certificate to upload.
- Accept Any Certificate to accept any cert.
Click Next.

Define the Target Details

Select the Target cluster from the drop-down.
Click Next.

Review & Add

Review the information.
Click Add.
Status updates can take up to three to five minutes, due to asynchronous status updates in the background.

Delete ZEDEDA Edge Kubernetes App Flows GitOps Repositories

After you add a git repo, you can delete it if you no longer need it. When a git repo is deleted, the already deployed apps associated with those git repos will also be deleted on clusters.

Click Edge Kubernetes > GitOps Repositories in the left panel.
Click the checkboxes next to the repos that you want to delete.
Click the ellipsis (…) at the top right of the page.
Select Delete from the drop-down menu.
Confirm the deletion action.

Next Steps

This is a series of articles. You will likely follow them in this order.

Was this article helpful?

0 out of 0 found this helpful