-
Notifications
You must be signed in to change notification settings - Fork 292
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
AKS Windows cannot support WinDSR because Azure CNI does not support loopbackDSR #2322
Comments
@immuzz, @keikhara would you be able to assist? Issue DetailsWhat happened: Reference: https://www.cni.dev/plugins/current/main/win-bridge/#network-configuration-reference What you expected to happen: How to reproduce it (as minimally and precisely as possible): Anything else we need to know?: Environment:
|
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment. |
This issue will now be closed because it hasn't had any activity for 15 days after stale. AbelHu feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion. |
@AbelHu , will WinDSR see the day in AKS eventually. Do you think this issue can be ignored and WinDSR be finally enabled again without this ? I'm not sure if any tracktion is getting done to fix this :( |
WinDSR is enabled by default in AKS for Kubernetes version 1.20.9+. You need to upgrade your cluster to 1.20.9+ to get it enabled in your AKS Windows nodes. |
How was this issue resolved? |
What happened:
Azure CNI does not support loopbackDSR so WinDSR is disabled in AKS Windows nodes by default when k8s version >= 1.20.0.
If WinDSR is enabled, users may hit this issue #2236.
Reference: https://www.cni.dev/plugins/current/main/win-bridge/#network-configuration-reference
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
):The text was updated successfully, but these errors were encountered: