Skip to content

Releases: kumahq/kuma

2.2.8

19 Mar 13:51
@kumahq kumahq
2.2.8
4a4e4a6
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.2.8

This is a patch release that every user should upgrade to.

Changelog

Contributors

lobkovilya and kumahq
Assets 2
Loading

2.6.2

19 Mar 13:50
@kumahq kumahq
2.6.2
4cef8d8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.2

This is a patch release that every user should upgrade to.

Changelog

Contributors

kumahq
Assets 2
Loading

2.5.3

20 Feb 13:34
@kumahq kumahq
2.5.3
This tag was signed with the committer’s verified signature.
slonka Krzysztof Słonka
SSH Key Fingerprint: eK7rEpWU/8eZyv5mKlGPB9P7OadztgZOYpLJyVWfZ8g Learn about vigilant mode.
23764bb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.5.3

This is a patch release that every user should upgrade to.

Changelog

Contributors

lukidzi and kumahq
Assets 2
Loading

2.4.6

20 Feb 14:25
@kumahq kumahq
2.4.6
This tag was signed with the committer’s verified signature.
slonka Krzysztof Słonka
SSH Key Fingerprint: eK7rEpWU/8eZyv5mKlGPB9P7OadztgZOYpLJyVWfZ8g Learn about vigilant mode.
e5ffd4d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.4.6

This is a patch release that every user should upgrade to.

Changelog

Contributors

lukidzi and kumahq
Assets 2
Loading

2.3.5

20 Feb 15:29
@kumahq kumahq
2.3.5
This tag was signed with the committer’s verified signature.
slonka Krzysztof Słonka
SSH Key Fingerprint: eK7rEpWU/8eZyv5mKlGPB9P7OadztgZOYpLJyVWfZ8g Learn about vigilant mode.
59b52bb
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.3.5

This is a patch release that every user should upgrade to.

Changelog

Contributors

lukidzi and kumahq
Assets 2
Loading

2.2.7

20 Feb 14:54
@kumahq kumahq
2.2.7
This tag was signed with the committer’s verified signature.
slonka Krzysztof Słonka
SSH Key Fingerprint: eK7rEpWU/8eZyv5mKlGPB9P7OadztgZOYpLJyVWfZ8g Learn about vigilant mode.
fc2c17e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.2.7

This is a patch release that every user should upgrade to.

Changelog

Contributors

lukidzi and kumahq
Assets 2
Loading

2.6.1

19 Feb 13:20
@kumahq kumahq
2.6.1
7b1269d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.1

This is a patch release that every user should upgrade to.

Changelog

Contributors

michaelbeaumont, lukidzi, and kumahq
Assets 2
Loading

2.4.5

06 Feb 11:58
@kumahq kumahq
2.4.5
4128477
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.4.5

This is a patch release that every user should upgrade to.

Changelog

Contributors

kumahq
Assets 2
Loading

2.3.4

06 Feb 11:58
@kumahq kumahq
2.3.4
baa08ae
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.3.4

This is a patch release that every user should upgrade to.

Changelog

Contributors

lukidzi and kumahq
Assets 2
Loading

2.6.0

01 Feb 12:28
@kumahq kumahq
2.6.0
d176c94
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
2.6.0

Get ready to elevate your Kuma experience with the release of Kuma 2.6.0, a jam-packed update that brings a myriad of exciting features to the table. From introducing a new MeshMetric policy to expanding policy targeting capabilities for MeshGateways, this minor release is packed with enhancements that will transform your network connectivity.

Check out the blog post for more details!

Upgrading

We strongly suggest upgrading to Kuma 2.6.0. Upgrading is straightforward through kumactl or Helm.
Be sure to carefully read the Upgrade Guide before upgrading Kuma.

Notable Changes

  • 🚀 Expanded Policy Targeting

    Kuma now allows a wider range of policies, including MeshCircuitBreaker, MeshFaultInjection, and MeshAccessLog, to target MeshGateways. This expands the granularity of policy enforcement and enables more fine-grained control over network traffic at the gateway level.

  • 🚀 MeshMetric Policy for Comprehensive Traffic Metrics

    Kuma introduces the new MeshMetric policy, which provides a centralized and consistent approach to collecting traffic metrics across all data plane proxies in a mesh. This policy simplifies the management of metrics configurations and ensures that all traffic data is captured uniformly.

  • 🚀 Streamlined MeshGateway Routing

    MeshHTTPRoute and MeshTCPRoute can now replace MeshGatewayRoute for configuring how a MeshGateway should process network traffic. This change provides greater flexibility and control over gateway routing rules.

  • 🚀 Modernized Default Policies

    The default legacy policies automatically created during mesh creation have been replaced with new, targetRef style policies.

  • 🚀 Enhanced Traffic Flow without mTLS

    When mTLS is not enabled for a mesh, traffic now flows by default, eliminating the need for a TrafficRoute policy.

  • 🚀 Improved GUI Experience

    Kuma 2.6.0 introduces a number of enhancements to the graphical user interface (GUI), making it more user-friendly and intuitive.

  • 🚀 Effortless Single-Zone to Multi-Zone Migration

    Kuma's zone federation allows you to effortlessly migrate from a single-zone deployment to a multi-zone configuration. This means you can start small with a single zone and gradually federate additional zones as your network grows, ensuring a smooth and controlled scaling process.

Changelog

Read more

Contributors

lahabana, jijiechen, and 11 other contributors
Assets 2
Loading