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
Winkernel proxier regression for dockershim CNIs that create v1 HNS endpoints #110591
Comments
@daschott: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig windows |
hi can I work on this |
/assign |
@imohitkumar1610 thanks, @daschott has already opened #110610 and #110590 |
/close |
@jsturtevant: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened?
#109981 has introduced a regression for Kubernetes clusters using dockershim as the runtime that invoke CNIs using the v1 HNS APIs. Winkernel proxier is unable to retrieve endpoints due to this hcsshim call failing to retrieve v1 HNS endpoints: https://pkg.go.dev/github.com/Microsoft/hcsshim@v0.8.22/hcn#ListEndpointsOfNetwork
This causes service proxy rules to not be created, as local endpoints would not be found.
Clusters using the containerD runtime and CNIs that leverage HCN APIs are not impacted.
Source:
We have noticed this is failing on our dockershim related tests: https://testgrid.k8s.io/sig-windows-1.23-release#aks-engine-windows-dockershim-1.23
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-aks-engine-azure-1-23-windows/1535071534270386176
What did you expect to happen?
Service proxy rules are created for all expected services
How can we reproduce it (as minimally and precisely as possible)?
Create a Kubernetes cluster with Windows and dockershim runtime
Anything else we need to know?
This issue does not occur on clusters with the containerD runtime (that use v2 CNI workflow creating HCN endpoints instead of HNS endpoints)
Kubernetes version
1.23, 1.22
Cloud provider
Reproduced on Azure, but all are impacted.
OS version
Windows Server 2019
Install tools
Container runtime (CRI) and version (if applicable)
Dockershim
Related plugins (CNI, CSI, ...) and versions (if applicable)
Azure CNI + dockershim. Any CNI creating v1 HNS endpoints will be impacted.
The text was updated successfully, but these errors were encountered: