-
Notifications
You must be signed in to change notification settings - Fork 87
Commit
Signed-off-by: Charly Molter <[email protected]>
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,104 @@ | ||
--- | ||
title: Kuma 2.3 release with MeshTCPRoute, GAMMA support and much more | ||
description: Kuma 2.3 release with MeshTCPRoute, GAMMA support and much more | ||
date: 2023-06-23 | ||
headerImage: /assets/images/blog/test-header.jpg | ||
tags: | ||
- Release | ||
--- | ||
|
||
We’re excited to announce the release of Kuma 2.3. This new minor release improves | ||
Check warning on line 10 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kuma 2.3. Upgrading is easy through `kumactl` or Helm. | ||
Check warning on line 12 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
## Notable features: | ||
|
||
* 🚀 targetRef policies are now working with `MeshGateway`. | ||
Check failure on line 16 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
* 🚀 `MeshTCPRoute` which enables to control traffic routing for TCP services. | ||
* 🚀 Helm improvements with more secure defaults. | ||
* 🚀 Possibility to skip creating default policies when creating a mesh. | ||
* 🚀 Performance improvements on Kubernetes. | ||
* 🚀 Add hosts selection predicates to `MeshRetry` | ||
* 🚀 Initial GAMMA routes support. | ||
* 🚀 Continuous improvements to the look and feel of the GUI | ||
* 🚀 Upgrade to Envoy 1.26 | ||
|
||
And a lot more! Checkout the full [release notes](https://github.com/kumahq/kuma/releases/tag/2.3.0) to see everything in this release. | ||
Check failure on line 26 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
### `MeshTCPRoute` | ||
|
||
In 2.2.0 we release [MeshHTTPRoute](https://kuma.io/docs/2.2.x/policies/meshhttproute/) which enabled traffic shaping and shifting of HTTP requests. | ||
Check warning on line 30 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
In this release we're adding the equivalent [`MeshTCPRoute`](https://kuma.io/docs/2.3.x/policies/meshtcproute/) for TCP traffic. | ||
Check warning on line 31 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
The usage is very similar to other targetRef policies. For example you can here do a progressive traffic routing of a service from one version to another. | ||
Check failure on line 33 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
```yaml | ||
apiVersion: kuma.io/v1alpha1 | ||
kind: MeshTCPRoute | ||
metadata: | ||
name: tcp-route-1 | ||
namespace: kuma-system | ||
labels: | ||
kuma.io/mesh: default | ||
spec: | ||
targetRef: | ||
kind: MeshService | ||
name: frontend_kuma-demo_svc_8080 | ||
to: | ||
- targetRef: | ||
kind: MeshService | ||
name: backend_kuma-demo_svc_3001 | ||
rules: | ||
- default: | ||
backendRefs: | ||
- kind: MeshServiceSubset | ||
name: backend_kuma-demo_svc_3001 | ||
tags: | ||
version: "1.0" | ||
weight: 90 | ||
- kind: MeshServiceSubset | ||
name: backend_kuma-demo_svc_3001 | ||
tags: | ||
version: "2.0" | ||
weight: 10 | ||
|
||
``` | ||
|
||
Note that cross zone routing hasn't been implemented yet. This will be done in the next release ([#6989](https://github.com/kumahq/kuma/issues/6989)). | ||
Check warning on line 67 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
Check warning on line 67 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
Check warning on line 67 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
Check warning on line 67 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
### `MeshGateway` support in new policy | ||
|
||
Up until now it was complicated to use the `targetRef` policies with the builtin gateway (read [#6560](https://github.com/kumahq/kuma/issues/6560) to understand why). | ||
Check warning on line 71 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
Check warning on line 71 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
Check failure on line 71 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
In the coming release this will be made even simpler with a new targetRef type `MeshGateway` which will enable you to identify a gateway by its name. | ||
You can check [MADR 027](https://github.com/kumahq/kuma/blob/master/docs/madr/decisions/027-meshgateway-targetref.md) for a teaser. | ||
|
||
### Initial GAMMA support | ||
|
||
[GAMMA](https://gateway-api.sigs.k8s.io/contributing/gamma/) is an initiative within the GatewayAPI community to create common interfaces for multiple service meshes. | ||
We believe this could ease the integration of service meshes with the rest of the Kubernetes ecosystem. | ||
This is the primary reason why Kuma has been active in this effort from the start. | ||
|
||
In 2.3.x we're very excited to announce support of HTTPRoute for [routing inside the Mesh](https://kuma.io/docs/2.3.x/explore/gateway-api/#service-to-service-routing). | ||
It's a simple feature but excited to see what people build around it! | ||
Check failure on line 82 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
### Governance changes | ||
|
||
The governance had not change since Kuma incubated in the CNCF. | ||
This meant that it wasn't really a mature and thought through process. | ||
We've now spent significant time thinking about our [GOVERNANCE](https://github.com/kumahq/kuma/blob/master/GOVERNANCE.md). | ||
We believe this will make how the Kuma community works more transparent and more welcoming to new contributors. | ||
|
||
By the way we are looking for production user stories, so if you have a good one please find us on Slack! | ||
Check failure on line 91 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
## Upgrading | ||
|
||
Be sure to carefully read the [Upgrade Guide](https://github.com/kumahq/kuma/blob/master/UPGRADE.md) before upgrading Kuma. | ||
|
||
## Join the community! | ||
Check failure on line 97 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
|
||
Join us on our [community channels](https://kuma.io/community/), including our official Slack chat, to learn more about Kuma. | ||
The community channels are useful for getting up and running with Kuma, as well as for learning how to contribute to and discuss the project roadmap. | ||
Kuma is a CNCF Sandbox project: neutral, open and inclusive. | ||
|
||
The community call is hosted [on the second Wednesday of every Month at 8:30am PDT](https://kuma.io/community/). | ||
Check failure on line 103 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|
||
And don't forget to follow Kuma [on Twitter](https://twitter.com/kumamesh) and star it [on GitHub](https://github.com/kumahq/kuma)! | ||
Check failure on line 104 in app/_posts/2023-06-23-kuma-2-3-0.md GitHub Actions / Lint docs
|