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

Incorrect weights for Ingress endpoint that has a service with many version #2563

Closed
jakubdyszkiewicz opened this issue Aug 13, 2021 · 12 comments
Closed

Incorrect weights for Ingress endpoint that has a service with many version #2563

jakubdyszkiewicz opened this issue Aug 13, 2021 · 12 comments
Labels
triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@jakubdyszkiewicz
Copy link
Contributor

Summary

Deploy Kuma Multizone with 2 zones (zone-1, zone-2) and the following setup

Zone 1:
Service Backend - version 1
Client

Zone 2:
Service Backend - version 2
Service Backend - version 3
Service Backend - version 4

The expected behavior is to generate EDS config for client with weight 1 for version 1 and weight 3 for ingress.
What happens instead is that Ingress has weight 1 because it's of different tag sets of services.
@lahabana
Copy link
Contributor

The test in #2564 will need to be reenabled as part of this fix.

@github-actions github-actions bot removed the bug label Nov 22, 2021
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 25, 2021
@github-actions
Copy link
Contributor

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting and removed triage/stale Inactive for some time. It will be triaged again labels Jun 29, 2022
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Aug 22, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 21, 2022
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Nov 21, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 20, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Feb 20, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 22, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label May 30, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 30, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting and removed triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again labels Sep 5, 2023
@lahabana
Copy link
Contributor

lahabana commented Sep 5, 2023

Putting back in pending because this might have been fixed by @jakubdyszkiewicz 's recent changes in the XDS generation of zone proxies

@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Sep 5, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Dec 5, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Dec 5, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Dec 5, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Mar 5, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Mar 5, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Mar 5, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jun 4, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 4, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya added triage/pending This issue will be looked at on the next triage meeting and removed triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again labels Jun 10, 2024
@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 Jun 10, 2024
@github-actions GitHub Actions
Copy link
Contributor

Automatically closing the issue due to having one of the "closed state label".

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
@jakubdyszkiewicz
Copy link
Contributor Author

Triage: it's not relevant for MeshService and MeshMultizoneService

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/rotten closed due to lack of information for too long, rejected feature...
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lahabana @slonka @jakubdyszkiewicz @lobkovilya @lukidzi