Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(meshtimeout): don't set default timeouts on inbound cluster and listener (backport of #12043) #12048

Closed
wants to merge 1 commit into from
Closed

fix(meshtimeout): don't set default timeouts on inbound cluster and listener (backport of #12043) #12048

wants to merge 1 commit into from

Commits on Nov 14, 2024

  1. fix(meshtimeout): don't set default timeouts on inbound cluster and l… 

    …istener (#12043)

We noticed that when a user upgrades to version 2.9.x without a default
MeshTimeout/Timeout policy, default timeouts are applied on inbound
clusters and listeners. This could disrupt the existing behavior of the
environment.

When no policy is present, we simply skip configuration and do not set
up the timeouts for inbound cluster or listener.

Fix #12033

<!--
> Changelog: skip
-->
<!--
Uncomment the above section to explicitly set a [`> Changelog:` entry
here](https://github.com/kumahq/kuma/blob/master/CONTRIBUTING.md#submitting-a-patch)?
-->

---------

Signed-off-by: Lukasz Dziedziak <[email protected]>
    @lukidzi @kumahq
    lukidzi authored and kumahq[bot] committed Nov 14, 2024
    Configuration menu
    Copy the full SHA
    ae78552 View commit details
    Browse the repository at this point in the history