Does our application need to be split into microservices for Kubernetes?

No. A well-structured monolith can be containerized and run on Kubernetes. Decomposition is worthwhile only when domain boundaries, scaling or independent release cycles justify the extra complexity.

Can databases remain outside the cluster?

Yes. Databases can run on dedicated VMs, bare metal or as a managed service. Availability, performance, backup, data sovereignty and the operating team's skills determine the right placement.

How do you avoid a pure lift-and-shift?

Before migration we capture operational problems and dependencies and define a target path for every component. Deployment, configuration, observability, backup and ownership are restructured, not just the execution location.

How is downtime planned?

Data volume, replication options, DNS, sessions and external dependencies become a cutover runbook. Where appropriate we use parallel operation, gradual switching or blue-green techniques.

Can WZ-IT modify the application code as well?

Yes. Our full-stack and backend expertise covers configuration, sessions, file storage, APIs, jobs and integrations. The migration therefore does not end at the infrastructure boundary.

Application modernization for Kubernetes: containerization and migration

WZ-IT analyzes architecture, data and operations, modernizes suitable components and migrates applications to Kubernetes or a smaller target platform with control.

Configure Kubernetes operations See the migration path

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

Migration as change

Define the right modernization path for each application

Between unchanged lift and shift and a complete rewrite are rehosting, replatforming, containerization and targeted revision of individual components. The migration path is defined for each part of the system.

Understand the application
Capture runtime, databases, file systems, external services, jobs, sessions and hidden operational dependencies.
Choose a path per component
Keep a VM, containerize, replatform or selectively refactor instead of rebuilding the entire system by default.
Move data safely
Plan migration windows, replication, schema changes, integrity validation and fallback together.
Restructure operations
Deployments, configuration, secrets, monitoring, backup and ownership become part of the target design.

Modernization modules

What is actually addressed on the way to Kubernetes

A production-ready migration covers the application, data, delivery, platform and operational responsibility.

Building blocks

Containerization & runtime
Multi-stage images, secure base images, health checks, resource profiles and stateless runtimes.
Databases & persistence
A conscious choice between platform, VM or managed service with backup and migration paths.
Configuration & secrets
Separate environment-specific configuration, manage secrets safely and minimize access.
Deployment & rollback
Reproducible builds, artifacts, staging, approvals and technically reliable fallback paths.
Interfaces & reachability
Map APIs, webhooks, DNS, certificates, egress and private dependencies into the target network.
Operability
Metrics, logs, traces, alerts, runbooks and restore tests before the production cutover.

Operational requirements

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.

Controlled refit

A migration path with verifiable transitions

Every phase produces a testable result. Application, data, delivery, observability and recovery are validated together before production cutover.

Discovery

Inventory code, runtime, data, interfaces, load and operational risks.

Target architecture

Classify components and make a reasoned Kubernetes suitability decision.

Container & platform

Build images, configuration, platform services and the delivery pipeline.

Migration & test

Move data and validate function, load, restore and rollback realistically.

Cutover & stabilization

Switch with control, observe closely and hand over operating documentation.

Starting pointOngoing operations

Kubernetes where it fits

The migration path follows risk and benefit

A database may remain on a VM, a monolith may initially only be containerized and individual services can follow later. We optimize the migration path for risk, benefit and operability.

Configure Kubernetes operations Discuss an application refit

Rehost, replatform and refactor may be combined within one system · Cutover, data consistency and rollback are resolved before migration day · The target architecture can deliberately combine Kubernetes, VMs and managed services

For professional secrecy holders

Operate Kubernetes in the Section 203 Managed Cloud

If Kubernetes processes client, patient or other professional secrets, WZ-IT plans the application, infrastructure, access, backups and ongoing operations within a purpose-built operating model.

View the Section 203 Managed Cloud →

Frequently asked questions

Clear answers on architecture, delivery, responsibilities and ongoing operations.

Knowledge base

In-depth guides for this building block

Knowledge base

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

View project

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.