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.
Implementation information
When no policy is present, we simply skip configuration and do not set up the timeouts for inbound cluster or listener.
Motivation
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.
Implementation information
When no policy is present, we simply skip configuration and do not set up the timeouts for inbound cluster or listener.
Supporting documentation
Fix https://github.com/kumahq/kuma/issues/12033