Table of Contents
🌏 中文版
OVHcloud spans VPS, Dedicated Servers, Public Cloud, Managed Kubernetes, databases, object/block/file storage, and hosted private cloud such as VMware and Nutanix. Public Cloud uses extensive OpenStack APIs and fits teams combining standard IaaS with public, dedicated, and private resources.
A Public Cloud instance is still your VM
The platform owns datacenters, hardware, and virtualization. Users own guest operating systems, SSH, patches, runtimes, application firewalls, deployments, monitoring, and data protection. Build reproducible instances with cloud-init or Packer, Terraform or OpenTofu, and immutable artifacts rather than accumulating manual production changes.
OpenStack APIs improve tool and concept portability, but provider extensions, flavors, networks, storage classes, and quotas still differ. OpenStack support does not create free multi-cloud. Validate identical IaC, images, and restore workflows in the alternative environment.
MKS owns the control plane; you own workers and workloads
The Managed Kubernetes architecture puts the control plane with OVHcloud and worker nodes and workloads with users. Node pools, requests and limits, RBAC, network policy, upgrade compatibility, persistent volumes, backups, and SLOs remain platform work.
MKS integrates Public Cloud load balancers, block or file storage, and private networks. Check region, plan, worker flavor, storage, and Kubernetes-version matrices before creation. A control-plane commitment does not spread Pods across failure domains automatically.
vRack is both composition and responsibility
Private networks connect same-region Public Cloud resources; vRack can connect regions, Dedicated Servers, and Hosted Private Cloud. That hybrid flexibility requires explicit IPAM, MTU, routing, gateways, DNS, firewalls, and failure-domain documentation.
Object Storage offers S3-compatible workflows while deployment mode, zone durability, versioning and lifecycle, SDK behavior, and restore still need validation. Managed databases own parts of HA, patches, and backups; applications own schemas, queries, connections, authorization, and recovery objectives.
OVHcloud fits teams prioritizing European data location, OpenStack, bare metal, and hybrid or private connectivity. A PaaS is simpler for source-to-URL apps; hyperscaler-serverless dependencies need replacement analysis. Lose an instance or worker, break vRack, and restore objects and databases to test audit, alarms, and support paths.
References
Loading...