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: create a cluster per destination setting for backends with filters #5269

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

fix: create a cluster per destination setting for backends with filters #5269

wants to merge 1 commit into from

Conversation

arkodg
Copy link
Contributor

@arkodg arkodg commented Feb 13, 2025

  • create a unique name by adding a new destination setting field
  • create a unique cluster per dest setting if the setting contains filters
  • reuse that for locality region name as well

Fixes: #5230

@arkodg
fix: create a cluster per destination setting for backends with filters
cd60338 
* create a unique name by adding a new destination setting field
* create a unique cluster per dest setting if the setting contains
  filters
* reuse that for locality region name as well

Signed-off-by: Arko Dasgupta <[email protected]>
@arkodg arkodg requested a review from a team as a code owner February 13, 2025 03:02
@arkodg arkodg marked this pull request as draft February 13, 2025 03:04
@guydc
Copy link
Contributor

guydc commented Feb 14, 2025

CP to 1.3.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

HTTPRoute weighted backends with filters attached sends traffic to the wrong backend
2 participants
@arkodg @guydc