Rahul Gupta

[](url [kube-proxy-windows-nrwgd.log](https://github.com/kubernetes-sigs/sig-windows-tools/files/9129385/kube-proxy-windows-nrwgd.log) ) The kubeconfig path seems misplaced C:\\hpc\\/var/lib/kube-proxy/kubeconfig.conf For calico I have used: https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/hostprocess/calico/calico.yml For kube-proxy I have used : https://github.com/kubernetes-sigs/sig-windows-tools/blob/master/hostprocess/calico/kube-proxy/kube-proxy.yml

I faced a similar issue. The generated token after Base64 decode appeared exactly the same as generated by "aws eks get-token --cluster-name " One thing I noticed was the presence...

Re-opening this issue. I am facing this issue with the following error: `Running C:\hpc\/cloud-node-manager.exe --node-name=cxp-workl-p5szn --use-instance-metadata=true --kubeconfig=C:\hpc\/var/lib/cpaw/kubeconfig.conf invalid configuration: unable to read certificate-authority C:\hpc\var\lib\cpaw\var\run\secrets\kubernetes.io\serviceaccount\ca.crt for default due to open C:\hpc\var\lib\cpaw\var\run\secrets\kubernetes.io\serviceaccount\ca.crt:...

/remove-lifecycle rotten

/reopen

@mboersma Thanks for this work. any guess when this will get merged

In the test URL, the secure label does not appear center aligned or looking at sth else?