The News
Mirantis announced the release of Mirantis Kubernetes Engine (MKE) 4 at KubeCon + CloudNativeCon NA 2024, introducing a fully open-source architecture powered by k0s. MKE 4 features enhanced security, a composable infrastructure, and integrated support for container and virtual machine (VM) workloads via KubeVirt. To read more, visit the product page here.
Analyst Take
The State of Enterprise Kubernetes Operations
As Kubernetes becomes the backbone of cloud-native infrastructure, enterprises are increasingly seeking solutions that offer flexibility and robust security without compromising performance. With over 300,000 nodes deployed globally, Mirantis Kubernetes Engine has been a trusted platform for mission-critical workloads across industries. However, the shift toward composable, modular architectures transforms companies’ deployment and management of Kubernetes clusters. MKE 4 embraces this trend, offering a fully open-source stack and a new composable architecture designed to meet the needs of diverse enterprise use cases.
MKE 4 Enhanced Approach to Kubernetes Infrastructure
The release of MKE 4 marks a significant evolution in Mirantis’ Kubernetes platform, shifting from a monolithic design to a fully composable architecture based on k0s. This change allows enterprises to customize their Kubernetes deployments with validated open-source components, ensuring optimal security, stability, and performance. The integration of KubeVirt further enhances MKE 4, enabling a unified platform for containerized and VM-based workloads. This converged approach reduces the complexity of managing hybrid environments and simplifies the transition for enterprises still running legacy VM workloads alongside cloud-native applications.
How Enterprises Previously Managed Kubernetes Challenges
In previous versions of MKE, the architecture was more rigid, requiring a standardized approach that often led to challenges in customization and scalability. Many enterprises had to rely on separate tools and manual processes to manage VM workloads and integrate security features, resulting in operational silos and increased management overhead. The lack of a composable architecture limited flexibility, making it difficult for organizations to tailor their Kubernetes environments to meet specific application requirements. Configuration drift and manual updates posed risks, often leading to unexpected downtime or security vulnerabilities.
The Benefits of MKE 4 for Developers and Platform Engineers
With the introduction of MKE 4, Mirantis provides a modern, flexible approach to Kubernetes operations. The fully open-source architecture and use of k0s as the core offer a standardized API and a declarative, automated lifecycle management process. The MKE Operator ensures continuous reconciliation of configurations, preventing drift and reducing the risk of manual errors. This shift to a more modular, customizable approach simplifies management and enhances security, with FIPS 140-2 encryption and robust observability options included out-of-the-box. For developers, the ability to seamlessly integrate container and VM workloads through KubeVirt streamlines application development and deployment, reducing the complexity of managing hybrid environments.
Mirantis’ Project 2A Bridging the Gap
Mirantis’ Project 2A is an open-source initiative aimed at providing an enterprise-grade solution for managing multiple Kubernetes clusters at scale. Designed as a unified, scalable platform, Project 2A enables consistent deployment, configuration, and maintenance of Kubernetes clusters across diverse environments, whether on-premises, in the cloud, or in hybrid setups. Acting as a “super control plane,” Project 2A centralizes the management of individual Kubernetes control planes. Through integration with the Cluster API provider ecosystem, it currently supports AWS, Azure, and vSphere, with plans to expand to additional providers. This approach offers full life-cycle management, streamlining the provisioning and security of Kubernetes clusters on a large scale.
At the core of Project 2A are several key components: the Hybrid Multi-Cluster Controller (HMC), the State Management Controller (SMC), and the Observability (OBS) module. The HMC handles multi-cluster deployment, configuration, and CRUD operations; the SMC manages beach-head services and policies; and OBS oversees monitoring and log management across clusters. Though originally named “HMC” in some documentation, Project 2A represents a more comprehensive framework designed around standardized templates, making Kubernetes cluster management both repeatable and secure.
Looking Ahead
As the Kubernetes ecosystem matures, the need for flexible, scalable, and secure infrastructure solutions is more critical than ever. Mirantis’ move toward a fully open-source, composable architecture positions MKE 4 as a key player in this evolving market. The convergence of container and VM workloads signals a broader trend toward unified platforms that can handle diverse application requirements without locking enterprises into a specific technology stack.
Looking forward, MKE 4’s flexible design and commitment to open-source components will likely drive increased adoption, especially among enterprises seeking to reduce vendor lock-in and leverage Kubernetes’ full potential. Integrating automated drift correction and customizable templates indicates that Mirantis is focused on simplifying Kubernetes management at scale. As organizations continue to scale their Kubernetes operations, MKE 4 offers a compelling solution that bridges traditional VM workloads and modern cloud-native applications, providing a unified, enterprise-ready platform for the future.
Redefining Application Development with Cisco’s AI Readiness Index
SOUTHWORKS: Empowering Cloud-Agnostic Application Development
Traefik Labs Introduces Mock API Sandbox as a Service for Seamless API Development
Solo.io Donates Gloo Gateway to CNCF, Launches Omni-Directional API Connectivity
Power Efficiency, GPU Shortages, and Sustainable AI KubeCon Roundtable Insights
