We are happy to announce Kuma's latest release, which is packed with features and improvements.
We strongly suggest upgrading, in order to take advantage of the latest and greatest when it comes to service mesh.
And a lot more! The full changelog is available here (opens new window).
We see many application teams deploy a service mesh for each of their applications to act as a logical boundary – each service mesh ensures only the services within the mesh can communicate with each other. Traditionally, these teams deployed a Delegated Gateway (opens new window) in their mesh to facilitate cross-mesh communication and authentication. Most chose Kong Gateway, but any API Gateway can work. The challenge with this approach is that each team must operate an API Gateway and configure it to securely connect to their mesh. And, while API Gateways are critical for connectivity at the edge of any environment, their full capabilities are not needed for connectivity between service meshes within an enterprise environment. Today's release of the Builtin Gateway's cross-mesh (opens new window) lets teams expose their meshes to other meshes, while keeping all traffic secured through the data plane using mTLS. And, configure all of their listeners and routes directly using Kuma policies.
We are also releasing a patch release of Kuma 1.5.x and 1.6.x with some critical bug fixes and an Envoy upgrade that contains important security fixes. Make sure to check the CHANGELOG (opens new window).
Join us on our community channels (opens new window), including our official Slack chat, to learn more about Kuma. The community channels are useful for getting up and running with Kuma, as well as for learning how to contribute to and discuss the project roadmap. Kuma is a CNCF Sandbox project: neutral, open and inclusive.
Be sure to carefully read the Upgrade Guide (opens new window) before upgrading Kuma.
Sign up for our Kuma community newsletter to get the most recent updates and product announcements.