Kubernetes · vCluster

Kubernetes platforms with virtual clusters

Separate clusters for every team are slow and expensive. Shared namespaces are cheaper but weakly isolated. CE Core builds Kubernetes platforms on vCluster, which gives each team a full virtual cluster inside one shared host cluster.

The problem

The two usual ways to run Kubernetes both create bottlenecks

Separate clusters

Days or weeks to provision, the same platform tools duplicated in every cluster, and a large fleet to operate.

Namespace isolation

Engineers lack cluster-wide permissions and CRDs, and the platform team becomes a bottleneck.

Idle environments

Development and test clusters keep running, and costing money, when nobody uses them.

The platform

How virtual clusters work

A virtual cluster has its own API server, so it is better isolated than a namespace and much cheaper than a separate cluster. vCluster is a certified Kubernetes distribution, so existing tools and pipelines keep working.

Provision in seconds

Teams get a full cluster on demand, without waiting for the platform team.

Shared platform stack

Run Istio, Cert Manager, OPA or Vault once on the host cluster instead of in every cluster.

Full admin access

Each tenant has admin rights inside its virtual cluster while the host stays protected.

Sleep mode

Idle pre-production clusters go to sleep and wake on demand.

Cluster per pull request

Ephemeral clusters for CI/CD and testing.

GPU sharing

Share GPU nodes between tenants for AI and ML workloads.

What CE Core does

From assessment to operations

  1. 01

    Assess

    We review your clusters, tenants, platform tools and cloud bill to find the savings.

  2. 02

    Design

    Host cluster layout, tenancy model, policies and the self-service workflow for your teams.

  3. 03

    Migrate

    We move workloads team by team, with no change to your deployment pipelines.

  4. 04

    Operate

    Upgrades, monitoring and support for the host and virtual clusters.

Proven in production

What the platform delivers

195 VMs → 1 cluster

Aussie Broadband consolidated Kubernetes from nearly 200 VMs onto a single bare-metal cluster and brought its VMware cost to zero.

Aussie Broadband · vCluster case study by LoftLabs

This result comes from a customer case study published by the technology vendor. It describes the vendor's customer, not a CE Core project.

Want to know what this would save you?

Request a free initial assessment. We reply within 24 hours.

Request an assessment
FAQ

Common questions

Other platforms we deliver:

Do we need to change our applications?

No. vCluster is a certified Kubernetes distribution, so you deploy to a virtual cluster with the same tools and manifests.

How is a virtual cluster different from a namespace?

A virtual cluster has its own API server and control plane, so tenants can install CRDs and use cluster-wide resources without affecting each other.

Can this run on our own hardware?

Yes. vCluster runs on any conformant Kubernetes host cluster, in the cloud or on bare metal.