Today, we're excited to announce Kong Mesh 2.13.
Kong Mesh 2.13 delivers full support for Mesh Identity for Kubernetes and Universal mode. Plus, it's been designated as a Long Term Support release, with support for a total of 2 years.
But first, what's Kong Mesh for the uninitiated?
Built on top of the open source Kuma service mesh, Kong Mesh is all about bringing simplicity and enterprise features to our customers. Kong Mesh is built for smooth operations with platform teams in mind, providing security, observability, and traffic control for modern, distributed applications. A single mesh can seamlessly span multiple zones: multiple cloud providers, Kubernetes clusters, and traditional server (VM / bare-metal) environments, while offering zero-trust security, multiple isolated mesh support, and global/remote control planes. Konnect Mesh Manager provides a global view across all your Mesh deployments.
With Kong Mesh, organizations can deploy with confidence and efficiency, managing mission-critical services reliably at high performance.
MeshIdentity defines how workloads in a mesh obtain their cryptographic identity. It separates the responsibility of issuing identities from establishing trust. With Kong Mesh 2.13, we now support MeshIdentity in both Kubernetes and Universal mode, as well as support for SPIRE as an identity provider.
Using the new rules selectors, you can apply Fault Injection rules selectively. For example, using the workload ID to inject a HTTP 500 error to 50% of the traffic received by your frontend workload:
When creating a MeshMultiZoneService, it can be difficult to confirm that your selectors correctly encapsulate your services across multiple zones.
We've introduced a MeshServicesMatched condition to MeshMultiZoneServiceStatus (MatchesFound and NoMatchesFound), which will tell you when it has successfully matched your selectors across zones.
During the installation of Kong Mesh, we automatically create the CA bundles for the webhooks we use during the lifecycle of your Mesh. We heard customer feedback, and we now support the ability for cert manager to manage the lifecycle of the certificates by setting controlPlane.tls.general.certManager.enabled to true during the Helm install.
For a deeper dive into a complete list of features, updates, and changes, please refer to the CHANGELOG here.
Want to see Kong Mesh in action? Request a demo or start using Kong Mesh today.
Thank you for your continued support and trust in our product!
We're very excited to announce Kong Mesh 2.12 to the world! Kong Mesh 2.12 delivers two very important features: SPIFFE / SPIRE support, which provides enterprise-class workload identity and trust models for your mesh, as well as a consistent Kuma R
Two of the main tenets of Zero Trust are encryption between services and managing the connections each service is allowed to use. Achieving this generally falls to running a service mesh in a Kubernetes cluster. Refactoring applications to run prope
Introduction One of the most common questions I get asked is around the relationship between Kong Gateway and Kuma or Kong Mesh . The linking between these two sets of products is a huge part of the unique “magic” Kong brings to the connectivit
What Is Terraform? Terraform is an infrastructure-as-code (IaC) tool developed by HashiCorp. It allows users to define and provision data center infrastructure using a declarative configuration language known as HashiCorp Configuration Language (HCL
We’re at it again, bringing more incremental improvements to Kong Mesh! Built on top of Kuma, Kong Mesh brings much-needed simplicity and production-grade tooling. Kong Mesh is built for smooth operations with platform teams in mind, providing secu
We’re excited to announce the release of Kong Mesh and Kuma 2.2. This new minor release adds some long-awaited enterprise features, more incremental improvements to our UI and policies, and many more minor features and bug fixes. In order to take
We’re excited to announce the release of Kong Mesh and Kuma 2.1! In this release, we’re shipping the full suite of new and improved policies announced (and started) in 2.0. Additionally, we’re launching some more great UX improvements in the UI and a