Effective Kubernetes for JakartaEE and Microprofile Developers

Developer Support

In this post, David Minkovski explores some best practices to get your deployment up and running on Kubernetes and Azure.


Kubernetes has become one of the most loved solutions for managing containers. But can you tell me why people love it?

Because it runs magic containers (essentially what you want) where you want. Whether on-premises or in the cloud (Azure), Kubernetes enables engineering teams to ship containers and scale and manage deployments and clusters easily.

Let’s look at some of those benefits some other time, OK? I am sure you will find plenty of resources out there explaining why K8S is great.

Many customers I have enjoyed working with are very fond of Java. And that makes perfect sense, especially if you consider Jakarta EE and MicroProfile.

These are widely adopted industry standard specifications by the Eclipse Foundation for high-quality enterprise software.

Java is almost 30 years old. There are a huge amount of software and legacy projects out there that want to — no, need to be migrated onto Kubernetes.

Well, how do you go about that?

This is precisely what this article aims to help you with.

For this, we will be using the repository by

Reza Rahman, which you can find here, and my humble fork.

This article will help you set up best deployment practices, amongst other things listed below:

  1. Auto-Scaling for Efficiency
  2. Auto-Discovery for Seamless Integration
  3. Load-Balancing for Even Workloads
  4. Self-Healing for Resilience
  5. Monitoring for Insights
  6. Operators for Application Management
  7. CI/CD Pipelines
  8. Running It on Azure

Continue reading the full post here.


Discussion is closed.

Feedback usabilla icon