Kubermatic launches version 2.19 of its Kubermatic Kubernetes Platform (KPP). The update introduces multi-cloud cluster management and new network configurations via Cillium CNI and Konnectivity.
The Kubermetic Kubernetes Platform (KKP) builds on the open source foundation of Kubernetes. Comparable platforms are SUSE Rancher, Red Hat OpenShift and VMware Tanzu. Each Kubernetes management platform provides proprietary features for the configuration, deployment and management of Kubernetes clusters.
The latest version of KPP has been launched. First, 2.19 introduces the ability to manage Kubernetes clusters across Azure, AWS and Google from a central dashboard.
Kubernetes clusters are always deployed in an on-premises- or managed cloud environment from Azure (AKS), AWS (EKS) and Google (GKE). A core component of KPP is the ability to deploy clusters in a cloud environment of choice. On the other hand, clusters have never been centrally manageable. Organizations resorted to multiple dashboards or DIY solutions.
As mentioned earlier, version 2.19 changes things for the better. Kubermatic features a new, centralized dashboard for clusters in different clouds.
Operating System Manager for air-gapped clusters
Second, 2.19 introduces support for Operating System Manager (OSM). The new module creates and manages operating system (OS) configurations of worker nodes in Kubernetes clusters. This makes it possible to deploy OS configurations separately from clusters.
The main application of OSM is an ‘air-gapped’ cluster. Air-gapped clusters are inaccessible on the network, which promotes security. The problem is that the operating systems of nodes can no longer be managed remotely. OSM solves the problem by decoupling OS configurations and nodes. A necessary workaround.
It is not yet possible to deploy air-gapped clusters entirely from Kubermatic. The introduction of OSM is nothing more than a step in the right direction. The organization expects to launch all other necessities in the next release.
Cilium CNI and Konnectivity for network configurations
Third, 2.19 introduces two native integrations with separate Kubernetes projects: Cilium CNI and Konnectivity. Collium CNI allows creating, securing, and monitoring network connections of containerized workloads. Cilium’s integration into Kubermatic makes some of its functionality available within Kubermatic.
Konnectivity is used to secure connections of the Kubernetes control plane and worker nodes with a TCP proxy. The most comparable solution is OpenVPN. The integration of Konnectivity makes the feature available for cluster configurations in Kubermatic.