Managed Kubernetes on your OpenStack

CNCF-conformant clusters on the infrastructure you already run: pick a region, a control plane model and node pools, and the platform provisions everything and hands back a kubeconfig. Upgrades, scaling and healing run continuously from there.

CNCF-conformant clustersDedicated or hosted control planesIn-place upgrades, autoscaling, self-healing
NameTypeHealthVersion
prod-eu-westSCPHealthyv1.34.0
edge-vigo-01HCPHealthyv1.34.0
staging-sharedHCPProvisioningv1.33.7
+ Create ClusterDownload Kubeconfig

Kubernetes on OpenStack shouldn’t be a platform project

Running Kubernetes on OpenStack by hand means gluing provisioners, cloud providers and upgrade tooling into a stack someone has to babysit; every cluster is a snowflake and every version bump is a risk. edgeContinuum ships that layer as a product: on-premises managed Kubernetes, declared through a console or API, kept in its desired state by the platform. Your team asks for a cluster; nobody builds one.

Provisioning

From quota to kubeconfig in minutes

Pick a region, a control plane model and node pools; the platform provisions the cluster on your OpenStack and hands back a kubeconfig. Download it and use kubectl in seconds, from the console, the API or Terraform. Every cluster lives inside a project, so quotas and roles apply automatically.

Console, API, TerraformNode poolsCNIs & pluginsAny region
kubernetes-7-julioHealthySCP
Cluster information
InfrastructureOpenStack Vigo
TypeSCP · c3-4
Versionv1.34.0
Network information
Pods CIDR10.244.0.0/16
Services CIDR10.96.0.0/12
Domaincluster.local
Download KubeconfigManage Control Plane
Hosted control planes

Control plane density, without the VM tax

Every dedicated control plane costs you VMs before the first workload runs. With hosted control planes, cluster control planes run pooled on shared infrastructure while worker nodes stay in each team’s project: more clusters per rack, same isolation for workloads. Choose per cluster; both models live side by side.

Higher densityPer-cluster choiceWorkers in your projects
Clusters
team-aHCP
team-bHCP
proddedicated
Pooled control planes
Worker poolsin each team’s project, on your OpenStack
Day-2 operations

Day-2 is the product

Clusters are declared, not built, so the platform can keep them true continuously: in-place Kubernetes upgrades, autoscaling node pools, and self-healing that replaces failed nodes without a ticket. Version skew across your fleet becomes a dashboard, not an audit.

In-place upgradesAutoscaling node poolsSelf-healingFleet-wide view

Upgrade in place

prod-eu-west: v1.33.7 → v1.34.0, node pools rolled automatically.

Autoscale

Node pools grow and shrink with load, inside the quota you set.

Self-heal

Failed nodes are detected and replaced; desired state wins.

Frequently asked questions

Are the clusters CNCF-conformant?
Yes. You get standard, conformant Kubernetes: your charts, operators and tooling work unchanged, and there is no fork to be locked into.
What do we need on the OpenStack side?
A working OpenStack you already operate. The platform connects to it and provisions clusters declaratively; you do not have to build or maintain your own provisioning stack.
How do upgrades work?
In place, driven by the platform: control plane first, then node pools roll automatically. You choose when; the platform does the sequencing and recovery.
Dedicated or hosted control planes: which should we pick?
Dedicated (SCP) gives a cluster its own control plane VMs; hosted (HCP) pools control planes on shared infrastructure for higher density. It is a per-cluster choice and both coexist on the same platform.
Can teams or clients create clusters themselves?
Yes, that is the point: clusters are self-service inside projects, quotas and roles you define, through the console, the API or Terraform. Usage is tracked per tenant.

Your first cluster in minutes, on your OpenStack

Request a free trial and provision a managed cluster against a lab OpenStack, or book a call and we’ll walk your case: control plane models, networking, upgrades.