[BPF] Topology Aware Hints implementation #7241
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marvin-tigera
added
docs-pr-required
ghost
mentioned this pull request
3 tasks
ghost
changed the title
ghost
marked this pull request as draft
tomastigera
requested changes
Jan 30, 2023
tomastigera
requested changes
Feb 1, 2023
tomastigera
changed the title
|
/merge-when-ready |
ghost
added
kind/enhancement
area/bpf
tomastigera
added
docs-not-required
ghost
marked this pull request as ready for review
ghost
mentioned this pull request
|
pls couold you rebase this branch on the current master? |
|
added 6 commits
February 16, 2023 17:49
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
fixes 7041
Running Calico with eBPF dataplane enabled and external kube-proxy disabled in the Kubernetes clusters on AWS. Would like to optimize the inter-AZ network costs and implement the solution offered by k8s Topology aware hints. It is understood that this feature is enabled in k8s 1.24 onwards.
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*label.docs-pr-required: This change requires a change to the documentation that has not been completed yet.docs-completed: This change has all necessary documentation completed.docs-not-required: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*label.release-note-required: This PR has user-facing changes. Most PRs should have this label.release-note-not-required: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.