> ## 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. # ZEDEDA Edge Kubernetes Service > Kubernetes cluster management and GitOps app delivery for edge environments using EVE-k. > [!NOTE] > > This feature is currently a work in progress. Some functionality may be incomplete or subject to change. ## Introduction ZEDEDA Edge Kubernetes Service provides Kubernetes cluster management for edge environments. It is built on EVE-k, the EVE-OS (Edge Virtualization Engine) variant that runs a K3S-based Kubernetes runtime on nodes. The service addresses the operational challenges of running Kubernetes outside the data center: resource-constrained hardware, intermittent or no connectivity, air-gapped deployments, and fleet management at scale (tens of thousands of clusters). ## Core Components ZEDEDA Edge Kubernetes Service is made up of two components that work independently or together. **ZEDEDA Edge Kubernetes Service** provisions and manages Kubernetes clusters at the edge. It handles cluster creation, node enrollment, version upgrades, and fleet-level groupings. This is the cluster infrastructure layer. **App Flows** provides GitOps app orchestration. App Flows monitors Git repositories and automatically deploys Helm charts to clusters when repository content changes. It enables declarative, version-controlled application delivery without direct cluster access. ### Primary use patterns * **GitOps-only app management:** Use App Flows to deploy and update Helm charts across clusters you already operate. ZEDEDA manages the delivery pipeline; your team manages cluster infrastructure separately. * **Full cluster and app fleet management:** Use ZEDEDA Edge Kubernetes Service together with App Flows to provision clusters, enroll nodes, organize cluster groupings, and automate app delivery end to end. ## EVE-k Operational Modes EVE-k is the EVE-OS variant introduced in EVE-OS 16.0 LTS to replace EVE-Kubevirt. Converting between EVE-kvm and EVE-k requires a fresh install. A node cannot switch between operational modes without a fresh install. EVE-k supports the following modes: | Mode | Description | When to use | | - | - | - | | **Single Node Mode** | Behaves like standard EVE-OS (EVE-kvm). Uses standard ZEDEDA manifests and the traditional Marketplace. | When you do not need Kubernetes or clustering. | | **Cluster Mode** | A cluster of EVE-k nodes that runs application instances with high availability and storage replication. Requires 1, 3, or more nodes. A 2-node cluster is supported only with two-node HA, which uses an etcd-only witness as the third vote. Perform cluster upgrades through ZCLI (the ZEDEDA command-line interface) only. The Clusters list shows this mode as **Edge Node Cluster**. | When you need edge high availability for application instances and do not need to expose the cluster's Kubernetes to users. You can enable Kubernetes access later without recreating the cluster. | | **ZEDEDA Edge Kubernetes Service Mode** | The same cluster with Kubernetes access enabled. The cluster still runs application instances, and in addition you can deploy Helm charts and GitOps workloads and use `kubectl`. Single-node or multi-node. The Clusters list shows this mode as **K8s Cluster**. Enabling Kubernetes access is permanent. | When you need Kubernetes-native app deployment, Helm charts, or GitOps at scale. | | **Imported Cluster Mode** | Third-party Linux Kubernetes clusters adopted for GitOps and Helm delivery only. They have no ZEDEDA edge nodes, so they never run application instances, and device orchestration is the customer's responsibility. ZCLI is not supported. The Clusters list shows this mode as **Imported K8s Cluster**. | When you are bringing an existing Kubernetes cluster under ZEDEDA application delivery. | EVE-k can also be used alongside third-party orchestrators such as Rancher. In that configuration, ZEDEDA manages device clustering and node lifecycle while Rancher handles app orchestration. ## Where to Find Kubernetes Features in Edge Infrastructure Services Edge Kubernetes features appear in several locations in the Edge Infrastructure Services sidebar: > [!NOTE] > > Most enterprises manage every cluster, with or without Kubernetes access, from **Infrastructure > Fleet > Clusters**. The separate **Kubernetes** item under **Infrastructure > Fleet** appears only while your enterprise has the Kubernetes Orchestration entitlement and no cluster has yet reported its Kubernetes mode to the console. After the first cluster does, the item is hidden and the Clusters page takes over. If you do not see **Kubernetes** in the sidebar, use **Clusters**. | Feature | Location | | - | - | | **Kube Clusters** | **Infrastructure > Fleet > Clusters**. On enterprises that still show the separate item, **Infrastructure > Fleet > Kubernetes**, Kube Clusters tab. | | **Cluster Groupings** | **Infrastructure > Fleet > Kubernetes**, Cluster Groupings tab. Not currently surfaced in the UI — this tab is temporarily hidden while it is finalized. | | **Installed Apps** | **Infrastructure > Workloads > Applications**, Kubernetes Apps tab | | **GitOps Repos** | **Infrastructure > Operations > GitOps Repos** | | **Secrets** | **Infrastructure > Workloads > Build > Secrets** | ## Next Steps > [card] [Create and Manage Kubernetes Clusters](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/create-and-manage-a-kubernetes-cluster.md) > > Create, import, configure, and delete Kubernetes clusters at the edge. > [card] [Manage Cluster Groupings](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/manage-kubernetes-cluster-groupings.md) > > Organize clusters into logical groupings for fleet-level management. > [card] [Manage Installed Applications](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/manage-kubernetes-installed-applications.md) > > View and manage Helm chart deployments across your clusters. > [card] [Kubernetes Marketplace](https://zededa.mintlify.site/new-ui/infrastructure-services/manage-app-from-kubernetes-marketplace.md) > > Browse and import Helm charts from the Kubernetes Marketplace. > [card] [GitOps Repositories](https://zededa.mintlify.site/new-ui/infrastructure-services/edge-kubernetes/create-gitops-repositories.md) > > Connect Git repositories for automated Helm chart delivery. > [card] [EVE-OS LTS Policy](https://zededa.mintlify.site/new-ui/infrastructure-services/eve-os/lts-policy.md) > > EVE-OS release schedule and support lifecycle.