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!
3 MIN READ
In 2019, my team at Kong introduced a new open source project called Kuma. Now a sandbox project of the CNCF, Kuma is a modern, universal control plane for service mesh based on Envoy.
As we celebrate Kuma’s achievements, I want to thank the Kuma community for your support and contributions!
In the past 12 months alone, Kuma had:
Kuma has developed a tight-knit community over the last couple of years. With 2,400 GitHub stars, Kuma receives support from 43 contributors and 800 Slack community members.
Our biggest contributors over the past year included:
Also, a special shout out to Austin Crawley-Edwards, who became a maintainer for Kuma this year!
In the last year, we went from release 0.7.1 to 1.3 and released hundreds of new features, including 70+ observability charts. Below are highlights from some of the major features shipped in the past 12 months.
Visualize all of your service traffic dependencies with information such as the number of requests and error rates. This new feature ships as a new official Grafana dashboard and can be installed automatically by running kumactl install metrics :
In addition to the traditional “strict” mode, this new mode allows for easier migration of existing applications into the service mesh by allowing more flexibility into how the data plane proxy certificates are validated on incoming requests.
Protect your services from aggressive traffic and downtimes to improve overall application reliability.
New L7 Traffic Routing policy to route – and modify – HTTP traffic per path, method, header or any other combination, with regex support. You can modify traffic before reaching the final destination too. This feature works in addition to the existing L4 traffic routing that Kuma provides.
Kuma’s hybrid capabilities allow different service meshes across Kubernetes and VM workloads and support within the same mesh. This, combined with Kuma’s multi-zone capabilities, allows users to run one control plane of Kuma with as many service meshes as you need on virtually every platform within your organization.
Kuma’s roadmap is heavily influenced by the user feedback in production. As such, we will:
Thank you to the Kuma Community for your support and contributions! Join the Kuma community on GitHub, Slack, Community Calls or Meetup if you haven’t already.