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:

type: MeshFaultInjection
mesh: default
name: default-fault-injection
spec:
 targetRef:
   kind: Dataplane
   labels:
     app: backend
 rules:
   - matches:
       - spiffeID:
           type: Exact
           value: "spiffe://my-mesh.us-east-2.mesh.local/ns/test/sa/frontend"
     default:
       http:
         - abort:
             httpStatus: 500
             percentage: 50

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](https://docs.konghq.com/mesh/changelog/)here.

Want to see Kong Mesh in action? [Request a demo](https://konghq.com/products/kong-mesh/request-demo)Request a demo or [start using Kong Mesh](https://docs.konghq.com/mesh/2.11.x/introduction/install/)start using Kong Mesh today.

Thank you for your continued support and trust in our product!