Mirantis recently announced the release of Mirantis Kubernetes Engine (MKE) 4, signaling a strategic pivot toward Kubernetes. In their official press release, Mirantis stated:
"For existing MKE users, upgrading to MKE 4 requires just one command or a single click. Users of MKE 3.7 can easily transition while keeping all workloads running. For Swarm users, Mirantis will continue support in MKE 3."
While Mirantis has pledged to maintain Swarm support in the MKE 3 series, the release of MKE 4—with its complete focus on Kubernetes—makes one thing clear: the clock is ticking for Swarm users. If you rely on Swarm as your container orchestration tool, now is the time to consider your next steps.
For those who, either by choice, or are required to remain on Swarm for legacy reasons, Portainer is the ideal solution. It offers continuity, a seamless transition path, and an unparalleled user experience for both Swarm and Kubernetes environments.
Mirantis’ decision to limit Swarm support to MKE 3 raises several concerns for Swarm users:
No New Features or Innovations
The focus on Kubernetes in MKE 4 means Swarm is effectively in maintenance mode. While Mirantis will address critical issues, there’s no guarantee of future enhancements or compatibility improvements.
Increasing Security Risks
Over time, relying on an older version of MKE with limited updates could expose your environment to unpatched vulnerabilities and compatibility issues with modern container runtimes.
Integration Challenges
The industry is rapidly converging on Kubernetes as the standard for container orchestration. New tools, technologies, and platforms are increasingly designed with Kubernetes in mind, leaving Swarm users at risk of being left behind.
Portainer bridges the gap between the simplicity of Swarm and the growing dominance of Kubernetes. Here’s why it’s the perfect fit for Swarm users facing this transition:
Portainer fully supports Docker Swarm, allowing you to continue managing your Swarm environments with ease. If you love Swarm’s straightforward approach to container orchestration, you can keep using it while benefiting from Portainer’s enhanced management capabilities.
Portainer doesn’t force you to choose between Swarm and Kubernetes. Instead, it allows you to:
Portainer combines the simplicity Swarm users love with the scalability of Kubernetes:
Portainer provides advanced functionality that makes it suitable for enterprise use:
Unlike Kubernetes, which often requires hiring specialized staff or investing in extensive training, Portainer empowers your existing team to manage Swarm and Kubernetes with minimal additional resources.
If you’re a Swarm user, switching to Portainer is not just a smart move—it’s a necessary one. Here’s why:
In summary, the release of MKE 4 marks a turning point for Docker Swarm users. While Mirantis has promised continued support in MKE 3, the writing is on the wall: Kubernetes is the future.
With Portainer, you don’t have to abandon the simplicity of Swarm or rush into the complexities of Kubernetes. Portainer provides the tools you need to manage Swarm today and transition to Kubernetes tomorrow—all without missing a beat.
For further information you might like to read about this customer's experience in migrating from Mirantis to Portainer. Read more.