When to Use EVE-k

Introduction

EVE-k is an EVE-OS variant with bare-metal Kubernetes support that enables AI workloads on Edge Node Clustering and ZEDEDA Edge Kubernetes Service, which serves as the infrastructure foundation for ZEDEDA Edge Kubernetes App Flows. EVE-k was introduced in EVE-OS 16.0 LTS to replace EVE-Kubevirt, which was introduced as early-access in EVE-OS 14.5.0 LTS. 

EVE-kvm is the original variant of EVE-OS, designed primarily for running traditional Virtual Machines (VMs) and containerized applications via shim VMs.

EVE-k was built on top of EVE-kvm code to add additional features like kubernetes runtime and clustering.

So  EVE-k = EVE-kvm + Kubernetes runtime  + clustering

EVE-k Modes

The EVE-k image functions in multiple modes to address different use cases.

Single Node Mode

In single node mode, EVE-k functions the same as EVE-kvm. It includes standard security and isolation features, and apps deploy in Virtual Machines (VMs) or shim VMs (containers). EVE-k functionality is the same as EVE-kvm in single node mode. You configure single node mode from the Edge Nodes menu in ZEDEDA Cloud GUI.

• App Format: Uses standard ZEDEDA proprietary application manifests.
• Marketplace: Uses the traditional edge apps marketplace.
• API: Uses existing EVE-API and ZEDEDA Cloud REST APIs.
• Terraform: Supported via existing Terraform provider functionality.
• Zcli: Uses existing zcli commands for edge nodes and apps functionality.

Cluster Mode

In cluster mode, you can create groups of EVE-k edge nodes for data replication, protection, and high availability (HA). You configure cluster mode from the Edge Node Clusters menu in ZEDEDA Cloud GUI. 

• Configurations:
  • Three-node clusters: All edge nodes are equal and participate in HA, compute, and data replication.
  • Three-node clusters with tie-breaker: A third edge node acts as a tie-breaker to reduce costs.
• App Format: Uses standard ZEDEDA proprietary application manifests.
• Marketplace: Uses the traditional edge apps marketplace.
• API: Uses enhanced EVE-API and ZEDCloud REST APIs for clustering.
• Terraform: Supported via enhanced Terraform provider functionality
• Zcli: Enhanced zcli to support edge node cluster CRUD operations including upgrades. 

ZEDEDA Edge Kubernetes Service Mode

This mode provides Kubernetes capabilities to the platform, allowing you to create single or multi-node Kubernetes clusters. It enables the deployment of cloud-native applications. You configure ZEDEDA Edge Kubernetes Service from the Edge Kubernetes menu in ZEDEDA Cloud GUI. 

• App Format: Uses industry-standard Helm charts, Kubernetes manifests, and GitOps.
• Marketplace: Use the Kubernetes Marketplace for Helm charts or GitOps Repositories for GitOps workflows.
• API: Uses enhanced ZEDEDA APIs to support Kubernetes clusters, Helm, and Git repositories.
• Terraform: Supported via enhanced Terraform provider functionality.
• Zcli: Enhanced zcli for kubernetes cluster CRUD operations including upgrades.

Imported Cluster Mode (Third-Party OS)

You can use ZEDEDA Edge Kubernetes App Flows for application orchestration on edge devices that do not run EVE-k. This mode allows you to import existing Linux-based Kubernetes clusters. Device orchestration is your own responsibility. You configure imported clusters from the Edge Kubenertes -> Clusters -> Import Clusters menu in ZEDEDA Cloud GUI.

• Management: The customer is responsible for device orchestration.
• App Format: Uses industry-standard Helm charts, Kubernetes manifests, and GitOps.
• Marketplace: Use the Kubernetes Marketplace for Helm charts or GitOps Repositories for GitOps workflows.
• API: Uses enhanced ZEDEDA APIs to support imported clusters and associated app formats.
• Terraform: Supported via enhanced Terraform provider functionality.
• Zcli: No support for import clusters

EVE-k  with third party Orchestrator (Rancher for now)

If you already have a third party orchestrator like Rancher and just want to use EVE-k for clustering and device management, you can still do that. The ZEDEDA Cloud cluster create API has been enhanced to include the rancher manifest URL. After a cluster is created, it will show up in your Rancher dashboard and you can do app orchestration from there.

• Management: The customer is responsible for app orchestration.
• App Format: Uses industry-standard Helm charts, Kubernetes manifests, and GitOps.
• Marketplace: Use the Kubernetes Marketplace for Helm charts or GitOps Repositories for GitOps workflows.
• API: Uses enhanced ZEDEDA APIs to support cluster creation with manifest url.
• Terraform: Supported via enhanced Terraform provider functionality.
• Zcli: No support for third party orchestrator

Next Steps

Device-specific installation, onboarding, and orchestration processes remain the same in the both variants, for a consistent experience between the two. See deployment prerequisites for slight differences.

You cannot perform an in-place software update to change an edge node from EVE-kvm to EVE-k or vice-versa. Switching between these variants requires a fresh installation on the edge node.

See naming conventions of EVE-OS images to understand the difference in available images.