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

Update MeshLoadBalancingStrategy docs to reflect actual k8s topology tags #1653

Closed
johnharris85 opened this issue Feb 13, 2024 · 4 comments
Closed

Update MeshLoadBalancingStrategy docs to reflect actual k8s topology tags #1653

johnharris85 opened this issue Feb 13, 2024 · 4 comments
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@johnharris85
Copy link
Contributor

Description

We use the example of k8s.io/az etc in the docs for awareness, but should use the topology.kubernetes.io/zone standard labels for clarity probably?

ref: https://docs.konghq.com/mesh/latest/policies/meshloadbalancingstrategy/#disable-cross-zone-traffic-and-prioritize-traffic-the-dataplanes-on-the-same-node-and-availability-zone
@johnharris85 johnharris85 added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Feb 13, 2024
@jakubdyszkiewicz
Copy link
Contributor

Depends on kumahq/kuma#9242

@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 Feb 19, 2024
@slonka slonka mentioned this issue Mar 14, 2024
Merged
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@github-actions 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.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 19, 2024
@github-actions 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.

@lukidzi
Copy link
Contributor

lukidzi commented Aug 19, 2024

@slonka I think it was fixed

@lukidzi lukidzi 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 Aug 19, 2024
@lukidzi lukidzi closed this as completed Aug 19, 2024
@lukidzi lukidzi 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 Aug 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature 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
3 participants
@johnharris85 @jakubdyszkiewicz @lukidzi