kube-proxy windows images is not correct (v1.29.8)

[thdrnsdk]

Describe the bug
A clear and concise description of what the bug is.
kube-proxy windows images is not correct (v1.29.8)

https://hub.docker.com/r/sigwindowstools/kube-proxy/tags?name=v1.29.8

the image size is 26.34 KB

and it's result was

Program 'kube-proxy.exe' failed to run: The file or directory is corrupted and unreadableAt line:1 char:1
+ .\kube-proxy.exe --version
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ .\kube-proxy.exe --version
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

that means this official image wrong

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

Kubernetes (please complete the following information):

• Windows Server version:
• Kubernetes Version:
• CNI:

Additional context
Add any other context about the problem here.

Tasks

Preview Give feedback

No tasks being tracked yet.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten