We are happy to announce the much-anticipated Kuma 0.6 release! This new release ships with major improvements, especially when it comes to supporting service meshes that can span across multiple clouds, multiple Kubernetes clusters and hybrid platforms (Kubernetes + VMs) in enterprise environments. Kuma has also been donated to the CNCF as a Sandbox project: the first Envoy-based service mesh to ever be donated to the foundation. Let’s unwrap these announcements.

Through a new partnership with Kong featuring native integration with Moesif, API providers will now have an enhanced Kong experience—enabling API teams to monitor their APIs and stay informed of issues and behaviors impacting their customers. With user behavior analytics, Kong customers can now track the entire customer journey with Moesif from initial sign up to the first API call and empower engineering and business teams with the product insights needed to experiment and take action.

Kong’s fast, lightweight and scalable API management solution helps improve developer productivity by automating the delivery of API management. One way Kong automates API management is through a continuous integration and continuous delivery (CI/CD) process by leveraging Kong’s decK (declarative configuration for Kong) and GitHub Actions. Kong’s decK provides a command line interface (CLI) to manage Kong in a declarative way.

When I started my journey into Kubernetes, you were always there for me when I needed to expose a service externally. We started small with just exposing one service, and you were dependable and easy to set up. But things have changed. My application has grown, and now the cluster has 10 services that need to be exposed externally. This has made communication difficult. I wonder what will happen when we have 50 services?

We are happy to announce the release of Kuma 0.5.1! This is a minor release that ships with improvements and bug fixes. For a complete list of features and updates, take a look at the full changelog.

Access control is an important function in our daily lives. Access control is provided in many different realms. For example, a physical door, a software program, or an API. Access control simply means that you are controlling who/what can access something. We’re going to focus this discussion around access control for an API. Businesses benefit from providing APIs to their internal (and external) developers.

Kong for Kubernetes is a Kubernetes Ingress Controller and a full-fledged edge-router which can route traffic to any destination of your choice. In addition to Ingress management, it provides enhanced security and management capabilities. With Kong, you can use Kubernetes not just for running your workloads but also for securing and monitoring connectivity between your workloads – all managed via Kubernetes manifests and CI/CD processes.

In today’s enterprise computing landscape, multi-cloud organizations are quickly becoming the norm rather than the exception. By leveraging an API-first strategy with a microservice-based architecture, companies can achieve significant speed to market across multiple clouds. In order to achieve this, container orchestration and a well-designed CI/CD strategy are essential components in this journey.

We are happy to announce the release of Kuma 0.5! We are particularly proud for this release since it introduces about 30 new features and many improvements and – as usual – every Kuma improvement is always available on both Kubernetes and Universal (VMs) modes. This version of Kuma also ships with a new logo for the project! The new logo for Kuma signifies a new era for the project, driven by more feature maturity as well as more adoption within the community.