See what makes Kong the fastest, most-adopted API gateway
Check out the latest Kong feature releases and updates
Single platform for SaaS end-to-end connectivity
Enterprise service mesh based on Kuma and Envoy
Collaborative API design platform
How to Scale High-Performance APIs and Microservices
Call for speakers & sponsors, Kong API Summit 2023!
4 MIN READ
We are happy to announce the first release for both Kong Mesh and Kuma in 2022, which is packed with features and improvements, including substantial performance improvements when running at scale.
We strongly suggest to upgrade, in order to take advantage of the latest and greatest when it comes to service mesh.
The full Kong Mesh changelog is available here.
The full Kuma changelog is available here.
Kuma 1.5.0 and Kong Mesh 1.6.0 ship with new troubleshooting capabilities in the GUI and CLI.
Kong Mesh – built on top of Kuma – is a multi-zone service mesh and since the beginning it supported the concept of Zone Ingress to allow traffic generated from a zone to enter another zone through a centralized ingress resource. Traffic that is coming outside of Kuma can enter the Mesh via Gateway data plane proxies.
With Kong Mesh 1.6 and Kuma 1.5, we have finally introduced a new Zone Egress resource, to channel traffic exiting a zone through a centralized egress component. Prior to this capability, the only egress functionality that Kuma supported was for egress traffic to exit the zone directly from the data plane proxies (which is still supported if we prefer the operational simplicity of not having to manage an additional component).
This gives us plenty of options when it comes to managing our ingress and egress traffic from within our Kong Mesh zones.
This release of Kong Mesh introduces a new builtin Gateway data plane proxy (technical preview), that can be used to expose mesh services to the outside world via an Envoy proxy. The new builtin gateway works across Kubernetes and VMs (like every other feature of Kong Mesh). Before we release this feature as GA in the next release, this new gateway will also natively support the new Kubernetes Gateway API specification, the successor of the older Ingress.
This also means that starting from today, Kong Mesh supports two gateway modes:
Delegated gateways have been supported for a long time, and they can be used to expose services to the outside world by delegating the capability to a 3rd party API Gateway, like Kong Gateway. This gives us plenty of options when it comes to exposing our services from within a Mesh:
The builtin gateway is currently experimental and is enabled with the kuma-cp flag --experimental-meshgateway or the environment variable KUMA_EXPERIMENTAL_MESHGATEWAY.
We always put lots of effort into improving the performance of Kong Mesh and Kuma to better sustain large service mesh deployments. On this release, we have significantly refactored our memory management capabilities and – by doing so – decreased memory consumption by 90%.
Below, you can observe the differences in memory consumption between Kuma 1.4.1 and the new 1.5.0, when new services are being added. These benefits are inherited by Kong Mesh 1.6.0.
Performance is a key focus area of Kong Mesh and Kuma, and this is one of many performance improvements that we have shipped into the project over the past few months, in order to make Kong Mesh easier than ever to scale in production environments.
Get in touch with Kong to learn more about Kong Mesh and how to build an enterprise service mesh. You can also download Kong Mesh and get started for free.
Learn how to make your API strategy a competitive advantage.