ExternalService with kuma.io/zone
tag behave differently w/ and w/o ZoneEgress
#6352
Labels
kind/feature
New feature
triage/rotten
closed due to lack of information for too long, rejected feature...
Description
If we have an external service with
kuma.io/zone: zone-2
and a client inzone-1
.When zone egress is enabled:
When zone egress is disabled:
actual:
expected:
Initially, I was thinking this is a bug, but apparently, this behavior is intended, and that's why it's an improvement.
The text was updated successfully, but these errors were encountered: