search

kubernetes-sigs / sig-windows-tools

Repository for tools and artifacts related to the sig-windows charter in Kubernetes. Scripts to assist kubeadm and wincat and flannel will be hosted here.
Apache License 2.0
123 stars 123 forks source link

A copy of kubeconfig.conf should be used in kube-proxy start.ps1 #341

Closed lzhecheng closed 1 year ago

lzhecheng commented 1 year ago

Describe the bug A clear and concise description of what the bug is.

kubeconfig.conf is mounted from kube-proxy ConfigMap so if you change the original file, it will be reset. As a result, before the windows kube-proxy pod becomes running, it will be failing for a few times.

For kube-proxy's start.ps1 script, to avoid ConfigMap mount reset, a copy of kubeconfig.conf should be used as kube-proxy.exe's arg.

To Reproduce Steps to reproduce the behavior: I tested on a capz cluster, here is the a windows kube-proxy pod status and log.

kube-system        kube-proxy-windows-jb2f9                                   1/1     Running   1 (3h27m ago)
E0823 04:52:11.072109    3916 server.go:494] "Error running ProxyServer" err="invalid configuration: unable to read certificate-authority C:\\C\\7abacb212fd13548771163698da621b18a127a9b2fba98503c46770dbd92256a\\var\\lib\\kube-proxy\\var\\run\\secrets\\kubernetes.io\\serviceaccount\\ca.crt for default due to open C:\\C\\7abacb212fd13548771163698da621b18a127a9b2fba98503c46770dbd92256a\\var\\lib\\kube-proxy\\var\\run\\secrets\\kubernetes.io\\serviceaccount\\ca.crt: The system cannot find the path specified."
E0823 04:52:11.072109    3916 run.go:74] "command failed" err="invalid configuration: unable to read certificate-authority C:\\C\\7abacb212fd13548771163698da621b18a127a9b2fba98503c46770dbd92256a\\var\\lib\\kube-proxy\\var\\run\\secrets\\kubernetes.io\\serviceaccount\\ca.crt for default due to open C:\\C\\7abacb212fd13548771163698da621b18a127a9b2fba98503c46770dbd92256a\\var\\lib\\kube-proxy\\var\\run\\secrets\\kubernetes.io\\serviceaccount\\ca.crt: The system cannot find the path specified."

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

windows kube-proxy pod runs successfully for the first time.

Kubernetes (please complete the following information):

Additional context Add any other context about the problem here.

lzhecheng commented 1 year ago

/assign

lzhecheng commented 1 year ago

/close

k8s-ci-robot commented 1 year ago

@lzhecheng: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/sig-windows-tools/issues/341#issuecomment-1690757868): >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.