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.

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

Closed
AbelHu opened this issue May 11, 2021 · 6 comments
Closed

Comments

@AbelHu
Copy link
Member

AbelHu commented May 11, 2021

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:

  • Kubernetes version (use kubectl version):
  • Size of cluster (how many worker nodes are in the cluster?)
  • General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
  • Others:
@AbelHu AbelHu added the windows label May 11, 2021
@AbelHu AbelHu self-assigned this May 11, 2021
@ghost
Copy link

ghost commented May 11, 2021

@immuzz, @keikhara would you be able to assist?

Issue Details

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:

  • Kubernetes version (use kubectl version):
  • Size of cluster (how many worker nodes are in the cluster?)
  • General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
  • Others:
Author: AbelHu
Assignees: AbelHu
Labels:

windows

Milestone: -

@ghost ghost added the action-required label Jun 5, 2021
@ghost ghost added the stale Stale issue label Aug 4, 2021
@ghost
Copy link

ghost commented Aug 4, 2021

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.

@ghost ghost closed this as completed Aug 19, 2021
@ghost
Copy link

ghost commented Aug 19, 2021

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 AbelHu reopened this Aug 20, 2021
@ghost ghost removed stale Stale issue action-required labels Aug 20, 2021
@ghost ghost added the action-required label Sep 14, 2021
@djsly
Copy link

djsly commented Oct 19, 2021

@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 :(

@AbelHu
Copy link
Member Author

AbelHu commented Oct 19, 2021

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.

@giskou
Copy link

giskou commented Nov 5, 2021

How was this issue resolved?
Should it be reopened due to #2608 (comment) ?

@ghost ghost locked as resolved and limited conversation to collaborators Dec 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants