MKS and cluster design
Size control-plane tier, regions, node pools, scaling, maintenance windows and failure domains.
vRack, load balancers & access
Design private networking, external services, OIDC and administrative access as one network model.
Storage & databases
Define block or object storage, persistent volumes, database placement and application-consistent backups.
GitOps, registry & supply chain
Organize images, Helm charts, signing, secrets and declarative deployments between environments.
Security & governance
Align OIDC, RBAC, network policies, Pod Security, image scanning and audit with the organization.
Observability & managed operations
Monitor and upgrade clusters, add-ons and workloads and operate them with tested recovery paths.
Operate Kubernetes on OVHcloud as a complete platform
WZ-IT designs and operates Kubernetes using OVHcloud Managed Kubernetes Service, public-cloud resources or dedicated infrastructure. We add networking, GitOps, security, backup and workload operations to the provider foundation.
Operating models
Managed control plane or private cluster: workloads still require operations
OVHcloud provides integrated Kubernetes and infrastructure products. We select the appropriate model and add every layer that remains necessary for a production application platform.
Managed Kubernetes Service
An OVHcloud-managed control plane with node pools and integration into public-cloud networking, storage and load-balancer services.
Self-managed Kubernetes
A private cluster on public-cloud instances or dedicated servers for alternative distributions and greater control.
Hybrid through vRack
Connect public cloud, bare metal and other OVHcloud resources through private network segments.
Application platform
Implement GitOps, registry, policies, observability and recovery consistently above the provider control plane.
Platform scope
From an OVHcloud cluster to a production application platform
We close the gap between a provisioned Kubernetes service and applications operated with defined responsibility.
In addition to the cluster, applications need defined processes for delivery, access, observability, recovery and technical ownership.
Delivery
GitOps, CI/CD, separate environments, approvals and reproducible rollbacks.
Network
CNI, network policies, ingress or gateway, DNS, TLS and private access.
Security
OIDC, RBAC, secrets, image validation, policies and traceable changes.
Observability
Metrics, logs, traces, alerting and SLOs for platform and applications.
Backup & restore
Cluster state, persistent data, restore tests and a documented recovery path.
Lifecycle
Updates, CVE assessment, capacity, costs and an agreed operating model.
Implementation
Connect OVHcloud services and Kubernetes ownership
OVHcloud Managed Kubernetes covers defined provider components. Cluster architecture, platform add-ons, workloads, data and recovery are designed and tested as complementary layers.
Service selection
Select managed Kubernetes, public cloud or bare metal from the requirements.Target architecture
Define region, node pools, vRack, storage, load balancers and access.Platform baseline
Integrate GitOps, registry, secrets, policies, observability and backup.Migration
Move applications, data and provider dependencies in controlled stages.Operations
Handle upgrades, capacity, backups, recovery and incidents with explicit ownership.Shared responsibility
Layered responsibility with OVHcloud Managed Kubernetes
The selected OVHcloud tier determines the provider scope. Platform configuration, workloads, data and business approvals remain separate areas of responsibility.
01
OVHcloud
- For Managed Kubernetes Service, manages the documented control-plane and service components according to the contracted product scope.
02
WZ-IT
- Owns the agreed architecture, cluster, add-on, security, backup and operating scope above and alongside the provider service.
03
Customer team
- Owns business decisions and, depending on the contract, application code and data; additional application responsibility can be assigned.
Managed is one layer
Responsibility above the managed control plane
Provider, WZ-IT and customer receive a documented assignment for node configuration, add-ons, identities, network policies, workloads, data, backups and incident processes.
Treat the provider service level and WZ-IT scope as separate commitments · Plan and test platform, workload and data recovery separately · Keep provider integrations declarative and document exit or migration paths
Frequently asked questions
Clear answers on architecture, delivery, responsibilities and ongoing operations.
- Yes. We design clusters and node pools, integrate networking, storage, identity, GitOps, observability and backup and assume the agreed platform or workload operations.
- Yes. A self-operated cluster on dedicated servers offers greater control over distribution, nodes and local resources but also increases responsibility for the control plane, lifecycle and infrastructure integration.
- The exact scope follows the contracted service and current responsibility matrix. The provider typically manages the control plane; configuration, workloads, data, permissions and backups remain wholly or partly with the customer or its operating partner.
- Yes. We map Kubernetes resources and proprietary cloud services separately, replace IAM, load-balancer, storage, database and observability dependencies and plan data migration and cutover.
- Depending on the architecture, we use private OVHcloud networks and vRack, OIDC, restrictive firewall and network policies and NetBird for identity-aware access to the API and internal platform services.
- Yes. Takeover starts with an audit of versions, node pools, networking, storage, add-ons, security, backups and workloads. Stabilization and a clearly scoped operating model follow.
Technical guidance
Distinguish OVHcloud MKS from self-managed clusters
The guide covers shared responsibility, vRack, node pools, storage, GitOps, backup and the choice between a managed service and a self-managed cluster.
Technical guidance
One platform. Six entry points.
Select infrastructure and operating model deliberately
Reviews & projects
Operations that visibly relieve customers
Customer feedback on monitoring, updates, maintenance, support and stable production systems.
WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
International
Built in Germany's Ruhr Valley. Running worldwide.
WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.
Selected projects
- LiveRemote access platform for distributed water treatment plantsABCO Water Systems · Australia · Secure Access & OT
- 81%AWS migration with substantially lower operating costsEVA Real Estate · UAE · Cloud exit & infrastructure
- 98%Provision new sites in minutes instead of hoursnextGYM GmbH · Germany · Automation & IoT

Read client reviews
- Secure your Proxmox & backup setup
- Virtualize with Managed Proxmox
- Build a high-availability Proxmox cluster
- Modernize your infrastructure - sovereign
- Plan a sovereign open-source stack
- Integrate a local AI solution
- Modernize your legacy software
- Cut cloud cost - up to −81%
- Design an open-source AI architecture
- Get collaboration fully managed
- Ship your prototype to production
- Connect sites and clusters securely
Enquiry
Which OVHcloud Kubernetes model fits your system?
Tell us the current state, workloads and desired ownership. We will assess managed Kubernetes, public cloud and bare metal.
- Straight with Timo and Robin - no sales team, no pitch
- A professional assessment of your situation
- Concrete next steps for infrastructure, software or AI
The conversation is free and non-binding.
WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.

















