Kuma recently came with their new version of 1.3.0. It has come up with several bug fixes and new features with this update. In this article, we will see those fixes and new features which will make users have a great experience with the product.
Buck up, and let’s start!
What is Kuma?
Kuma is a CNCF sandbox project which we can use as a modern Envoy-based service mesh that can run on every cloud, in a single or multi-zone capacity, across both Kubernetes and VMs. It has broad universal workload support. It has a combination with native support for Envoy as its data plane proxy technology (but with no Envoy expertise required). Kuma helps in providing modern L4-L7 service connectivity, discovery, security, observability, routing and more across any service on any platform, databases included.
Kuma is easy to use, with built-in service mesh policies for security, traffic control, discovery, observability and more. Kuma ships with an advanced multi-zone and multi-mesh support that automatically enables cross-zone communication across different clusters and clouds. It also automatically propagates service mesh policies across the infrastructure. Enterprise organizations are adopting Kuma to support distributed service meshes across the application teams on Kubernetes and VMs.
The devs have engineered Kuma to be powerful yet simple to use, reducing the complexity of running a service mesh across every organization with unique capabilities like multi-zone support, multi-mesh support, and a gradual and intuitive learning curve.
The latest release comes with the migration of DiscoveryRequest/Response in KDS to V3. Also, we see the addition of rewriting dns persistence to allow virtual outbound. Again, we see the moving of kumactl logging arguments to where they can get a parameter. The addition of route and virtual host configuration helpers will help a lot to the users. We can also see the simplification of resource-gen.go by generating ResourceDescriptor. We also see the replacement of netcat with a test server.
With this release, we can see the removal of the provided ca cert validation. The use of kuma-sd in kumactl install metrics is a new feature that came along with this release. We can also see the addition of a new datasource to kumactl install metrics. Once again, there is the addition of rate-limit to outbound interfaces. With version 1.3, there is the bumping of alpine in /tools/releases/dockerfiles. There is also the annotation of required fields in proto files. Again, we see the removal of MADS v1alpha1. Furthermore, we also see the parametrizing of Kuma tracing in ZipkinCollectorURL.
Version 1.3 brings the addition of the number of services to usage stats. Also, we observe the addition of the permissive mTLS mode. The opening of CAProvider and MeshValidator for extensions is visible with this update. There is the addition of an entity for virtual-outbound. For kuma-cp, we can see the upgradation of GUI to the new version. The feature of building Kuma on Windows will help a lot of Microsoft OS users. This version also brings the addition of CA backend stats in Dataplane and Mesh Insights.
The version of 1.3 brings the configuration of split listener across source files. It also brings the addition of simple HTTP connection configurers. The release brings an essential addition of virtual host domain name configurer. The feature of returning instance and cluster IDs in kuma-cp API statuses and intermediate CA support gets an addition. We get consistent use of utils package for protobuf wrappers with version 1.3 and get certificates over ADS.
Another feature of the configuration of SNI on ExternalService gets an introduction through this release. We can also see the addition of importas to golangci-lint. Again, the addition to resource-gen.go generation of kds options and resource-gen.go generation of kumactl options brings more stability. This whole release improves resource-gen by auto-generating ws code. We also see the simplification of resourceWsDefinition and server init. Finally, we can see the making of port for validation consistent.
Version 1.3 brings the removal of an extra endline in the traffic log default template. It also fixes the issue where TLSInspector is causing tcp healthcheck failures. Another issue where you need to print a newline with a transparent proxy setup message gets a fixing. Now, you will be able to set up
zap.Development() in debug log. Also, there will be no missing key for kv in reports logging. This version will allow kuma-specific const to get an override, and the flaky test for locality aware load-balancing gets a fixing for tests. Again, there will be no avoiding of nil dereferencing in the dp validator.
We see a fixing of subscription finalizer for rev 2. Again, this version brings the fixing of DP tracking lock consistency. We also see fixing the issue where a deleted default policy gets a creation on Kuma CP restart. This version fixes the kumactl generate dataplane proxy-type flag deprecation message. We also see the fixing of the addition of the owner when creating ZoneIngressInsight. This version again brings light on the fixing of hijacker merge labels. There will now be a clarification of invalid resource type messages. Furthermore, we can see the fix where we see the implementation TextMarshaler for JSON keys. Finally, we can see the stopping of adding outbounds to dp for vips.
We can see the changes, fixes, and features that significantly impact this release throughout the article. We see that users will benefit a lot because of the introduced features and the bugs that got fixed. I know you want to try it out. Get Kuma on your environment by clicking here. If you want to contribute to the project, you can do that by clicking here. Have a blast with Kuma, and I will see you next time.
Read more of our blogs below. Happy learning!