Skip to main content

Edge provider

Deploy customer workloads at distributed edge sites without managing a separate cluster at each one. Telecommunications providers, ISPs, and edge compute operators use this model to run low-latency services at POPs, exchange points, and remote facilities from a single central control planeControl PlaneThe container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers. In vCluster, each cluster has its own control plane components.Related: API Server, vCluster.

Customer access model: Each customer gets an isolated cluster whose workloads schedule onto dedicated edge nodes. Worker-node model: Private nodes, joined from each edge site.

Typical stack: Central Standalone (HA) as the control plane cluster. Central vClustervClusterAn open-source software product that creates and manages clusters within Kubernetes infrastructure. vCluster provides tenant isolation capabilities while reducing infrastructure costs.Related: Cluster, Control plane cluster Platform. Worker nodes at each edge site joined to the central control plane using VPN. Tenant control planes run centrally; pods schedule onto edge nodes.

Edge distribution architecture: central control plane with clusters scheduling pods onto distributed edge site nodes
Central control plane managing customer workloads across distributed edge sites

What makes this path different: The compute is distributed but the control plane is not. Your ops team manages the full fleet from one place. Tenants get a standard Kubernetes experience regardless of which edge site their workload lands on.

Day 0: Design decisions​

DecisionRead nextOutcome
Decide whether each customer needs a tenantTenantsA tenant scopes which sites, node types, and images a customer can use. Use one per customer where separate organizations share the edge fleet.
Design the central-edge topologyStandalone deployment, VPNCentral Standalone hosts all tenant control planes. Edge sites contribute worker nodes over VPN.
Define edge site requirementsNode requirementsDocument the OS, networking, and connectivity requirements for each edge site before joining nodes.
Plan node labeling and schedulingPrivate NodesLabel nodes by site, region, or tier so tenant workloads can be scheduled to the correct edge location.
Plan tenant isolation at edgevNode docsDecide whether edge workloads need runtime isolation, especially for edge sites shared by several tenants.

Day 1: Stand up the first edge site​

  1. Deploy vCluster Standalone centrally and move to HA.
  2. Install vCluster Platform and configure SSO and permissions.
  3. Establish VPN connectivity to the first edge site.
  4. Join edge site nodes to the central control plane clusterControl plane clusterThe Kubernetes cluster that hosts the virtualized control planes for clusters. The control plane cluster is operated by the platform provider and is completely invisible to tenants. There are no shared control plane nodes, no in-cluster agent pods, and no lateral path between tenant environments. With shared nodes, this cluster also runs tenant workloads alongside the control plane pods — the same node pool is used for both.Related: Cluster, Control plane cluster, Cluster. Apply site labels.
  5. Create a template that schedules customer workloads to the correct edge site using node selectors or affinity rules.
  6. Provision a test cluster. Validate that pods land on the intended edge nodes.
  7. Document the site onboarding playbook. Repeat steps 3-6 for each additional edge site.

Day 2: Operate​

OperationRead next
Monitor edge nodes and cluster workloadsFleet Observability, other architectures
Add and remove edge sitesSite onboarding playbook (internal), VPN
Upgrade clusters and PlatformUpgrade vCluster, upgrade Platform
Handle site connectivity failuresPlatform HA, multi-region Platform