OVH Clusters

Ankra supports provisioning fully managed Kubernetes clusters on OVH Cloud. You can create clusters with configurable control planes, workers, and networking — then scale workers up or down as needed.

Prerequisites

Before creating an OVH cluster, you need two credentials:

OVH API Credential

OVH Cloud API credentials (application key, application secret, consumer key, and project ID). See OVH API Credentials.

SSH Key Credential

An SSH public key for server access. You can provide your own or let Ankra generate one. See SSH Key Credentials.

Creating an OVH Cluster

Via the Platform UI

A guided wizard walks you through creating an OVH cluster — select credentials, pick a region, choose instance flavors (general purpose, CPU-optimized, or RAM-optimized), set control plane and worker counts, and launch.

Navigate to Clusters

Go to Clusters in the Ankra dashboard and click Create Cluster.

Select OVH Cloud

Choose OVH Cloud as the provider.

Select Credentials

Pick your OVH API credential and SSH key credential from the dropdowns. You can also create new credentials directly from the wizard.

Choose Region

Select an OVH Cloud region (e.g., Gravelines, Strasbourg, Beauharnois, Warsaw, London, Frankfurt). Each region shows the location and country.

Configure Nodes

Set your cluster topology:

Gateway — Instance flavor for the SSH gateway (e.g., b2-7)
Control Plane — Count and flavor (e.g., 1x b2-15)
Workers — Count and flavor (e.g., 2x b2-15)

The wizard shows vCPUs, RAM, disk, and hourly cost for each flavor to help you choose.

Create & Track Progress

Click Create to start provisioning. A live progress view tracks every step — network creation, gateway setup, control plane provisioning, worker provisioning, k3s installation, and Ankra Agent setup. The cluster appears with an offline state until provisioning completes, then transitions to online.

Managing from the Dashboard

Once your OVH cluster is online, you can manage it directly from the Ankra dashboard:

Scale workers — Go to Cluster Settings → General to scale worker nodes up or down
Upgrade Kubernetes — Upgrade the k3s version from cluster settings
Deprovision — Delete the cluster and all OVH resources from the Danger Zone in cluster settings

Via the CLI

# Create credentials first
ankra credentials ovh create --name my-ovh-cred --project-id <project-id>
# You will be prompted for application key, application secret, and consumer key

ankra credentials ovh ssh-key create --name my-ssh-key --generate

# Create the cluster
ankra cluster ovh create \
  --name my-cluster \
  --credential-id <ovh-credential-id> \
  --ssh-key-credential-id <ssh-key-credential-id> \
  --region GRA7 \
  --control-plane-count 1 \
  --control-plane-flavor-id b2-15 \
  --worker-count 2 \
  --worker-flavor-id b2-15

Via the API

curl -X POST https://platform.ankra.app/api/v1/clusters/ovh \
  -H "Authorization: Bearer $ANKRA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-cluster",
    "credential_id": "<ovh-credential-id>",
    "ssh_key_credential_id": "<ssh-key-credential-id>",
    "region": "GRA7",
    "control_plane_count": 1,
    "control_plane_flavor_id": "b2-15",
    "worker_count": 2,
    "worker_flavor_id": "b2-15",
    "distribution": "k3s"
  }'

Cluster Configuration Options

Parameter	Default	Description
`name`	required	Unique cluster name
`credential_id`	required	OVH API credential ID
`ssh_key_credential_id`	required	SSH key credential ID
`region`	required	OVH Cloud region
`network_vlan_id`	`0`	VLAN ID for the private network
`subnet_cidr`	`10.0.1.0/24`	Subnet CIDR range
`dhcp_start`	`10.0.1.100`	DHCP allocation range start
`dhcp_end`	`10.0.1.200`	DHCP allocation range end
`gateway_flavor_id`	`b2-7`	Instance flavor for the gateway
`control_plane_count`	`1`	Number of control plane nodes
`control_plane_flavor_id`	`b2-15`	Instance flavor for control planes
`worker_count`	`1`	Number of worker nodes (1–10)
`worker_flavor_id`	`b2-15`	Instance flavor for workers
`distribution`	`k3s`	Kubernetes distribution
`kubernetes_version`	latest	Kubernetes version (optional)

OVH Cloud Regions

Region	Location
`GRA7`	Gravelines, France
`GRA9`	Gravelines, France
`GRA11`	Gravelines, France
`SBG5`	Strasbourg, France
`BHS5`	Beauharnois, Canada
`WAW1`	Warsaw, Poland
`DE1`	Frankfurt, Germany
`UK1`	London, United Kingdom
`SGP1`	Singapore
`SYD1`	Sydney, Australia

OVH Instance Flavors

Flavor	vCPUs	RAM	Description
`b2-7`	2	7 GB	Suitable for gateways
`b2-15`	4	15 GB	General purpose, good for control planes and workers
`b2-30`	8	30 GB	Higher performance workloads
`b2-60`	16	60 GB	Memory-intensive workloads

Available flavors vary by region. Check the OVH Cloud catalog for your region’s offerings.

Scaling Workers

You can scale worker nodes between 1 and 10 for any online OVH cluster. Scaling up adds new instances and installs Kubernetes. Scaling down removes workers starting from the highest index.

The cluster must be online with no active operations before scaling.

Via the Dashboard

Go to your cluster → Settings → General and adjust the worker count. The new count is applied immediately and you can track progress in the Operations tab.

Check Current Workers

ankra cluster ovh workers <cluster_id>

Response:

{
  "worker_count": 2,
  "min": 1,
  "max": 10
}

Scale Workers

ankra cluster ovh scale <cluster_id> 4

Response:

{
  "previous_count": 2,
  "new_count": 4
}

Upgrading Kubernetes Version

You can upgrade the Kubernetes (k3s) version on all nodes in an OVH cluster. Upgrades are applied to control plane nodes first, then workers.

Only k3s clusters are supported for version upgrades.
Downgrades are not supported — k3s downgrades require an etcd snapshot restore.
You can only upgrade one minor version at a time (e.g., v1.33.x to v1.34.x, not v1.33.x to v1.35.x).
The cluster must be online with no active operations.

Via the Dashboard

Go to your cluster → Settings → General to see the current k3s version and trigger an upgrade.

Check Current Version

ankra cluster ovh k8s-version <cluster_id>

Response:

{
  "current_version": "v1.34.4+k3s1",
  "distribution": "k3s"
}

Upgrade Version

ankra cluster ovh upgrade <cluster_id> v1.35.1+k3s1

Response:

{
  "previous_version": "v1.34.4+k3s1",
  "new_version": "v1.35.1+k3s1",
  "nodes_affected": 3
}

Deprovisioning

Deprovisioning deletes all OVH resources (instances, networks, SSH keys) and removes the cluster from Ankra.

This action is irreversible. All data on the cluster will be permanently deleted.

Via the Dashboard

Go to your cluster → Settings → General → Danger Zone and click Deprovision Cluster. You will be asked to confirm before the operation begins.

Via CLI or API

ankra cluster ovh deprovision <cluster_id>

Architecture

An OVH cluster provisions the following infrastructure:

Component	Description
Gateway	Jump server for secure SSH access to cluster nodes
Private Network	Isolated VLAN for inter-node communication
Control Plane(s)	Kubernetes control plane instances
Worker(s)	Kubernetes worker instances for running workloads
SSH Keys	Deployed to all instances for access

All nodes are deployed within a private OVH network. The gateway provides the only external SSH access point.

Troubleshooting

Common Issues

Issue	Solution
Cluster stuck in provisioning	Check OVH API credentials and project quota
Cannot scale workers	Ensure cluster is online and no operations are running
Invalid API credentials	Re-validate at OVH API Console
Flavor unavailable	Try a different region or flavor

OVH Cloud Quotas

OVH Cloud has default resource limits per project. If provisioning fails, check your quotas in the OVH Control Panel:

Instances
Networks / VLANs
SSH Keys

Contact OVH support to increase limits if needed.

Get Started

Guides

Clusters

Stacks & Add-ons

GitOps

Kubernetes Resources

Platform Features

Team & Settings

Integrations

Prerequisites

OVH API Credential

SSH Key Credential

Creating an OVH Cluster

Via the Platform UI

Managing from the Dashboard

Via the CLI

Via the API

Cluster Configuration Options

OVH Cloud Regions

OVH Instance Flavors

Scaling Workers

Via the Dashboard

Check Current Workers

Scale Workers

Upgrading Kubernetes Version

Via the Dashboard

Check Current Version

Upgrade Version

Deprovisioning

Via the Dashboard

Via CLI or API

Architecture

Troubleshooting

Common Issues

OVH Cloud Quotas

Get Started

Guides

Clusters

Stacks & Add-ons

GitOps

Kubernetes Resources

Platform Features

Team & Settings

Integrations

​Prerequisites

OVH API Credential

SSH Key Credential

​Creating an OVH Cluster

​Via the Platform UI

​Managing from the Dashboard

​Via the CLI

​Via the API

​Cluster Configuration Options

​OVH Cloud Regions

​OVH Instance Flavors

​Scaling Workers

​Via the Dashboard

​Check Current Workers

​Scale Workers

​Upgrading Kubernetes Version

​Via the Dashboard

​Check Current Version

​Upgrade Version

​Deprovisioning

​Via the Dashboard

​Via CLI or API

​Architecture

​Troubleshooting

​Common Issues

​OVH Cloud Quotas

Prerequisites

Creating an OVH Cluster

Via the Platform UI

Managing from the Dashboard

Via the CLI

Via the API

Cluster Configuration Options

OVH Cloud Regions

OVH Instance Flavors

Scaling Workers

Via the Dashboard

Check Current Workers

Scale Workers

Upgrading Kubernetes Version

Via the Dashboard

Check Current Version

Upgrade Version

Deprovisioning

Via the Dashboard

Via CLI or API

Architecture

Troubleshooting

Common Issues

OVH Cloud Quotas