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
1
Create Cluster
Go to Clusters → Create Cluster and pick OVHcloud’s Cloud Managed action.
2
Credential & Region
Select the OVHcloud credential and a region (for example
GRA9). Regions load live from OVHcloud.3
Node Pools
Define one or more worker pools: name, node flavor (with live pricing), count, labels, and autoscaling bounds.
4
Kubernetes & Plan
Pick a Kubernetes version or keep the default, choose the control-plane plan (
free or standard), and set the update policy.5
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.
OVHcloud MKS options
Day-2 operations
Node pools, upgrades, and deletion work from the CLI, portal, or API. The CLI examples use--provider ovh_mks:
PATCH .../node-pools/{name} endpoint. See Managed Kubernetes - day-2 operations for the shared mechanics.