OVHcloud Managed Kubernetes (MKS)

OVHcloud Managed Kubernetes (MKS) runs on OVHcloud Public Cloud. OVHcloud runs the control plane; Ankra provisions the cluster, then manages everything on top - node pools, Kubernetes upgrades, addons, stacks, GitOps, and AI-assisted operations. This page covers OVHcloud MKS specifically. For the shared concepts across all managed providers - live options, discovery/import, and day-2 API patterns - see Managed Kubernetes.

Why OVHcloud MKS with Ankra

Free or standard control plane - pick the OVHcloud control-plane plan that fits the workload.
Private networking and anti-affinity - attach a private network and spread nodes with anti-affinity where supported.
Live pricing and options - regions, Kubernetes versions, and node flavors are fetched live with your OVHcloud credential.

Prerequisites

OVHcloud application keys with a Public Cloud project (project_id), stored in Ankra. See OVH API Credentials. GitOps is optional: connect a repository at creation and Ankra commits the cluster’s stack definitions to Git.

Creating an OVHcloud MKS cluster

Portal
CLI
API

Create Cluster

Go to Clusters → Create Cluster and pick OVHcloud’s Cloud Managed action.

Credential & Region

Select the OVHcloud credential and a region (for example GRA9). Regions load live from OVHcloud.

Node Pools

Define one or more worker pools: name, node flavor (with live pricing), count, labels, and autoscaling bounds.

Kubernetes & Plan

Pick a Kubernetes version or keep the default, choose the control-plane plan (free or standard), and set the update policy.

GitOps (optional) & Create

Optionally connect a Git repository, then create. Ankra runs OVHcloud preflight checks, provisions the cluster, retrieves the kubeconfig, and installs the Ankra Agent.

ankra cluster managed create \
  --provider ovh_mks \
  --name my-ovh-cluster \
  --credential-id <ovh-credential-id> \
  --location GRA9 \
  --node-pool-name workers \
  --node-pool-size b2-7 \
  --node-pool-count 2

Plan, private network, anti-affinity and update policy are set from the portal or the API; --autoscaling with --autoscaling-min and --autoscaling-max sets the initial pool’s bounds. The CLI accepts ovh_mks (and the ovh-mks alias).

curl -X POST https://platform.ankra.app/org/clusters/managed/ovh_mks \
  -H "Authorization: Bearer $ANKRA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-ovh-cluster",
    "credential_id": "<ovh-credential-id>",
    "location": "GRA9",
    "kubernetes_version": "1.32",
    "node_pools": [
      {"name": "workers", "size": "b2-7", "count": 2}
    ],
    "ovh_mks": {"plan": "free", "anti_affinity": false, "monthly_billed": false}
  }'

OVHcloud MKS options

Field	Description
`ovh_mks.plan`	Control-plane plan (`free` or `standard`)
`ovh_mks.private_network_id`	Attach the cluster to a private network
`ovh_mks.anti_affinity`	Spread nodes with anti-affinity
`ovh_mks.monthly_billed`	Bill nodes monthly instead of hourly
`ovh_mks.update_policy`	Node update policy

Verify

The create progress view follows the control plane, the node pools, kubeconfig retrieval and the Ankra Agent install. The cluster shows Online once the agent has connected. Then point kubectl at it through Ankra - this needs a Cluster Access grant - and check that every node is Ready:

ankra cluster kubeconfig add <cluster-name> --use
kubectl get nodes

See Accessing Clusters with kubectl.

Day-2 operations

Node pools, upgrades, and deletion work from the CLI, portal, or API. The CLI examples use --provider ovh_mks:

# scale a pool to a fixed count
ankra cluster managed node-pool scale <cluster_id> workers --provider ovh_mks --count 5

# upgrade the cluster
ankra cluster managed upgrade <cluster_id> --provider ovh_mks --version 1.32

# delete the cluster
ankra cluster managed delete <cluster_id> --provider ovh_mks

Autoscaling bounds are set from the portal, with ankra cluster managed node-pool update --autoscaling --autoscaling-min <n> --autoscaling-max <n>, or with the PATCH .../node-pools/{name} endpoint. See Managed Kubernetes - day-2 operations for the shared mechanics.

Importing an existing MKS cluster

Already running OVHcloud MKS? Discover clusters in your Public Cloud project and adopt them into Ankra without touching them. Discovery and import run from the portal, the CLI (ankra cluster managed discover|import --provider ovh_mks) or the API - see Managed Kubernetes - importing existing clusters.

Get Started

Concepts

Create and Run Clusters

Ship Your App

Stacks and Add-ons

Observe and Troubleshoot

Ankra AI

Connect Tools

Source Control

Security and Access

Cost and Backups

Organisation and Account

Reference

OVHcloud Managed Kubernetes (MKS)

Why OVHcloud MKS with Ankra

Prerequisites

Creating an OVHcloud MKS cluster

OVHcloud MKS options

Verify

Day-2 operations

Importing an existing MKS cluster

​Why OVHcloud MKS with Ankra

​Prerequisites

​Creating an OVHcloud MKS cluster

​OVHcloud MKS options

​Verify

​Day-2 operations

​Importing an existing MKS cluster

​Related

Why OVHcloud MKS with Ankra

Prerequisites

Creating an OVHcloud MKS cluster

OVHcloud MKS options

Verify

Day-2 operations

Importing an existing MKS cluster

Related