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.

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

ExternalService with kuma.io/zone tag behave differently w/ and w/o ZoneEgress #6352

Closed
lobkovilya opened this issue Mar 27, 2023 · 1 comment
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@lobkovilya
Copy link
Contributor

Description

If we have an external service with kuma.io/zone: zone-2 and a client in zone-1.

  • When zone egress is enabled:

    client(zone-1) -> egress(zone-1) -> ingress(zone-2) -> egress(zone-2) -> external service
    
  • When zone egress is disabled:

    actual:

    client(zone-1) -> external service
    

    expected:

    client(zone-1) -> ingress(zone-2) -> external service
    

Initially, I was thinking this is a bug, but apparently, this behavior is intended, and that's why it's an improvement.

@lobkovilya lobkovilya added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Mar 27, 2023
@jakubdyszkiewicz
Copy link
Contributor

Closing. This will be considered as a part of #6330

@jakubdyszkiewicz jakubdyszkiewicz closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/rotten closed due to lack of information for too long, rejected feature... and removed triage/pending This issue will be looked at on the next triage meeting labels Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...
Projects
None yet
Development

No branches or pull requests

2 participants