Post

From Monolith to Kubernetes Workloads

We finally made the leap: moved a legacy Java monolith to Kubernetes.

Here’s what helped:

  • Broke out background jobs as independent CronJobs
  • Converted WAR to fat JARs using Spring Boot
  • Used ConfigMaps + Secrets to manage environment parity

Our CI pipeline triggered builds and published images to a private registry. Helm took care of deployment templates.

One pain point? Stateful storage. We had to rethink our use of local file writes and convert some features to S3-based persistence.

But overall, the transition was smoother than expected — with improved rollout control and monitoring.

This post is licensed under CC BY 4.0 by the author.