Proxmox provides compute, virtualization, storage and infrastructure HA. Kubernetes standardizes deployments and the lifecycle of modern applications. WZ-IT designs and operates both layers as one system.
The following are trademarks of their respective owners: Proxmox VE (Proxmox Server Solutions GmbH). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
Kubernetes services
From target architecture through infrastructure and delivery to ongoing operations. Each page explores one part of the same accountable platform.
Proxmox provides compute, storage and networking for virtual machines, LXC and dedicated Kubernetes nodes. This becomes an application platform for containerized, horizontally scalable or consistently delivered workloads.
Clusters, nodes, ZFS or Ceph, network segments, Proxmox Backup Server and infrastructure monitoring.
Control plane, worker pools, CNI, ingress, storage classes, registry and platform services.
Legacy VMs, databases, appliances and containerized applications can coexist in their appropriate operating models.
Proxmox protects the VM layer. Kubernetes resources, persistent data and applications receive complementary backup and recovery procedures with tested restores.
The layers are designed separately but validated together. This keeps failure domains, capacities and responsibilities understandable.
Size workloads, availability, growth and failure domains.
Define compute, storage, network, HA, quorum and backup architecture.
Provision Kubernetes nodes automatically and install the platform baseline.
Bring applications, data and access paths onto the platform with control.
Coordinate, monitor and document upgrades across both layers.
The concrete stack follows the target design. What matters is the clean separation and integration of infrastructure, cluster and application.
Node roles, quorum, resource reserves and maintainability for a single site, HA or multiple locations.
ZFS, Ceph, CSI, storage classes and databases with clear performance and recovery strategies.
VLANs, bridges, CNI, MetalLB or external load balancers, DNS, TLS and segmentation.
Terraform, Ansible, Cloud-Init and declarative cluster configuration instead of manual exceptions.
PBS, etcd, persistent volumes and application-consistent backups with documented restore paths.
Hardware, hypervisor, nodes, Kubernetes and workloads in a coordinated monitoring and alerting model.
In addition to the cluster, applications need defined processes for delivery, access, observability, recovery and technical ownership.
GitOps, CI/CD, separate environments, approvals and reproducible rollbacks.
CNI, network policies, ingress or gateway, DNS, TLS and private access.
OIDC, RBAC, secrets, image validation, policies and traceable changes.
Metrics, logs, traces, alerting and SLOs for platform and applications.
Cluster state, persistent data, restore tests and a documented recovery path.
Updates, CVE assessment, capacity, costs and an agreed operating model.
Knowledge base
Two layers, one operation
Proxmox and Kubernetes have different lifecycles. We coordinate maintenance, capacity, backup and incident response across both levels without mixing their responsibilities.
Move to the part of the platform that matters most for your current initiative.
Clear answers on architecture, delivery, responsibilities and ongoing operations.
Yes, when compute, storage, network, failure domains and lifecycle are sized appropriately. Proxmox provides the virtualization and infrastructure layer; Kubernetes runs on top as its own platform with explicit resource and availability requirements.
Both can make sense. VMs offer flexible provisioning, isolation and easier hardware maintenance. Bare metal can fit specialized performance, GPU or network requirements. We decide based on workloads and operating goals.
Not necessarily. Ceph is useful with suitable node counts, networks and HA requirements. For smaller platforms, ZFS, replicated storage or external storage systems can be the simpler and better solution.
No. PBS protects the infrastructure and VM layer. Kubernetes state, persistent data and application-consistent backups are also required. Recovery has to be designed and tested across all layers.
Yes. We review resources, networking, storage, quorum, backup and operating condition and design the Kubernetes layer on that basis. If the foundation is insufficient, it is stabilized before the cluster is built.
Whether you have an existing Proxmox cluster or need a new private-cloud foundation, we assess architecture, capacity and operating model.
No risk: worst case, you leave with a clearer understanding of your project than before.


“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.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep & Robin Zins
Managing Directors of WZ-IT
