Closed yahbouss closed 2 months ago
Can you try building the image on your own? We have not built every version of the flannel images
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Describe the bug I am trying to create kubernetes cluster with 1 windows node and ubuntu node. the ubuntu node joined successfully and it's working but the windows is not. I ran the hack/DebugWindowsNode.ps1 and it showed me an issue with kube-proxy.exe not running as a service
here is my investigation till now:
To Reproduce Steps to reproduce the behavior: I ran :
Expected behavior win-node should be ready, instead it is not ready
Kubernetes (please complete the following information):
Additional context When nothing worked, i tried changing the version of the kube-proxy, reverting it back, checking the logs of the containerd in the windows, and this is the log: