Kuma 1.0.4 Released With Transparent Proxying For VMs & New Retry Policy
CTO and Co-Founder
Make no mistake! This is a minor release in name only: we are happy to announce the release of Kuma 1.0.4 with many improvements and new non-breaking features, and we suggest to upgrade to start using the greatest and latest.
Notable Improvements in 1.0.4
🚀 One-click transparent proxying mode for VMs in universal mode.
🚀 A new “Retry” policy to improve the resiliency of our traffic.
Improvements when deleting a zone in a multi-zone deployment.
Collecting both “kuma-dp” and “envoy” versions in both the CLI and the GUI.
Improvements to resource validations, ingress data plane proxies,
Groundwork for Envoy v3 XDS support.
And much more!
For a complete list of features and updates, take a look at the full changelog.
Note: Kuma 1.0.4 also includes one update that was silently shipped and released in Kuma 1.0.3 (soft-launched earlier this month): default Envoy timeouts have been temporarily disabled on a per-route basis in preparation for a new “Timeout” policy that will ship in January which will allow us to set customizable timeouts for different traffic paths.
In this new release we are finally bringing transparent proxying support to universal mode for VMs and Bare Metal, in addition to the pre-existing support in Kubernetes. This is done by supporting a one-click installation of iptables rules on the machine where “kuma-dp” will be running. With transparent proxying in universal mode we can finally avoid describing explicit “outbound” entries in our data plane proxy specifications.
Join us on our community channels to learn more about Kuma, including our official Slack chat. The community channels are useful to get up and running with Kuma, as well as to learn how to contribute to and discuss the project roadmap. Kuma is a CNCF Sandbox project: neutral, open and inclusive.