Blog

Today, we announce the latest release of Kubermatic Kubernetes Platform (KKP)- both Enterprise Edition (EE) and Community Edition (CE). The community driven CE is completely open source with users around the world, some of them running thousands of clusters. The EE has exclusive features for large …

With Kubermatic Kubernetes Platform 2.19, we introduced support for the Cilium CNI for both, the enterprise and the community edition of our platform.

Quick network response times have become the standard.

33 milliseconds - The amount of time needed for a piece of information to travel from Spain to the U.S. and back via the Marea undersea cable.

It is with great excitement that we announce the latest release of Kubermatic Kubernetes Platform (KKP). With KKP 2.20, we aimed to make KKP more robust by improving naming conventions and further strengthening code quality.

Kubernetes is all about sharing machines between applications. Typically, sharing machines requires ensuring that two applications don’t try to use the same ports. Managing port allocation across multiple developers is difficult at scale, and exposes users to cluster-level issues they can’t control.

Ever since it became more than an atmospheric mass of condensed water vapor, cloud has provided apps the ability to automatically scale with it and significantly impact its use. Cloud enables teams to operate applications without having to constantly and manually modify the underlying resources to fit the actual demand.

With Kubernetes becoming an ubiquitous platform for running software at scale, an obvious but sometimes overlooked topic is security. Over the past years, several guidelines to secure Kubernetes clusters have been released.

It is with great excitement that we announce the latest release of Kubermatic Kubernetes Platform (KKP). The 2.19 release focuses on enhancing KKP’s edge and hybrid cloud capabilities and networking performance, enabling you to harness the power of Kubernetes with even greater ease and comfort.

In the last post, we discussed Kubernetes Autoscaler in KKP as well as its usage. We also showed you how to install Kubernetes Autoscaler on a KKP Cluster. Now let’s take it a step further and show you how to annotate the MachineDeployments which you want the Autoscaler to recognize.

In a nutshell, it’s a component that automatically adjusts the size of a Kubernetes Cluster so that all pods have a place to run and there are no unneeded nodes.