Skip to main content
Reference material for OVH clusters.

Cluster Configuration Options

The fields of POST /api/v1/clusters/ovh. The portal’s create form sets most of them; see Create a Cluster.

OVH Cloud Regions

The regions enabled on each OVH project differ. A region that is not enabled on the project’s private network fails the reconcile during network setup. List the regions a credential can actually deploy in with ankra cluster ovh regions --credential-id <credential_id> before creating a cluster.

OVH Instance Flavors

The defaults come from the current b3/c3 generation: Other sizes of the same lines include b3-8, b3-32 and b3-64 (general purpose), c3-8 and c3-16 (CPU-optimised) and r3-16, r3-32 and r3-64 (RAM-optimised). Older projects may still offer the b2/c2/r2 generation.
Available flavors vary by region. The portal’s create form lists what the chosen region offers, with prices, under Exact server type. Check the OVH Cloud catalog for the full list.

Node Group API Reference

Node Actions API

See Restart a node and Bastion for how to use them.

Disabled k3s Components API

The k3s_disabled_components list set at create can grow on a running k3s cluster. The body is the complete list and has to contain every entry already stored; an unknown or repeated entry is a 422 validation error pointing at the entry. applies answers: “The platform’s maintenance read lane compares each control plane’s k3s server config against this list within about five minutes and flags the ones missing an entry; the reconcile lane then patches the config and restarts k3s on one control plane at a time, in the cluster’s k8s update chain. Control planes already carrying every entry are not touched. The list only grows: re-enabling a bundled component is not supported yet, so a change that removes a stored entry is refused, and so is any change while a node update, version upgrade or node restart is still in progress on the cluster.” The refusals answer 409 with the detail shown:

Architecture

The managed network gateway (<cluster>-network-gw) is the nodes’ router and NAT; the bastion (<cluster>-bastion, or <cluster>-gateway on clusters created before the rename) is an SSH jump host only. See What Ankra created in your project.