-
Notifications
You must be signed in to change notification settings - Fork 3.4k
nodeinit: remove workaround for Azure CNI bridge mode #34870
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
nodeinit: remove workaround for Azure CNI bridge mode #34870
Conversation
Azure CNI has defaulted to transparent mode since 2020 (see Azure/azure-container-networking#709) and today all AKS clusters on a supported version (1.27 or later) are running in transparent mode. Cilium no longer needs workarounds to force Azure CNI from bridge mode to transparent mode, so remove these steps from the nodeinit script. Signed-off-by: Will Daly <widaly@microsoft.com>
/test |
Hi @wedaly , iust a bit curious, why Azure convert from bridge mode to transparent mode? Isn't the performance of bridge mode better than Linux routing? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice cleanup, thanks!
/ci-aks |
@ruicao93 this part of the AKS docs is a pretty good description of the problems with bridge mode: https://github.com/MicrosoftDocs/azure-docs/blob/32ecba35211b602b74596d6753b3fcd4a3a90f41/articles/aks/faq.md#benefits-of-transparent-mode (it's since been deleted from the public docs, but you can see it in the git history). |
Azure CNI has defaulted to transparent mode since 2020 (see Azure/azure-container-networking#709) and today all AKS clusters on a supported version (1.27 or later) are running in transparent mode.
Cilium no longer needs workarounds to force Azure CNI from bridge mode to transparent mode, so remove these steps from the nodeinit script.