Could not find host mac address for 0.0.0.0

[jeroenlandheer]

Describe the bug
A clear and concise description of what the bug is.
kube-proxy v1.21.x crashes with the message:

F0729 15:22:54.388647    3828 server.go:489] unable to create proxier: unable to create ipv4 proxier: Could not find host mac address for 0.0.0.0, hostname: ****-k8s-w3, clusterCIDR : 10.244.0.0/16, nodeIP:0.0.0.0

To Reproduce
Steps to reproduce the behavior:

• Upgrade from 1.20.9 to 1.21.0

Expected behavior
No error message

Kubernetes (please complete the following information):

• Windows Server version: Microsoft Windows [Version 10.0.17763.1577] (1809)
• Kubernetes Version: 1.21.3
• Docker: 20.10.0
• Flannel: 0.12.0

[dfateyev]

Kube-proxy-windows is broken starting from 1.21.0.
The workaround is to downgrade worker to 1.20: use v1.20.0 in kube-proxy.yml and PrepareNode.ps1 call.

[jsturtevant]

This is tracked in k/k: kubernetes/kubernetes#100966

fixed by kubernetes/kubernetes#101047 with a backport in progress to 1.21: kubernetes/kubernetes#103783

The work around for 1.21 is #147

[dfateyev]

@jsturtevant any chances that the fix will land 1.21.4? (since automatic merge to release-1.21 above is still open)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[jeroenlandheer]

It looks like in the latest release this has been fixed. Thanks :)