Hi!
I’m testing Calico for Windows on your Kubernetes cluster on premises with this document.
- kubernetes verison: v1.19.0
- calico version: v3.16.1
I’ve joinned windows worker node on calico k8s cluster and it seems ok with calico on linux cause’ I’ve tested with nodeport for nginx.
kubectl get no --show-labels
NAME STATUS ROLES AGE VERSION LABELS
wc-lnxnode-c Ready 28h v1.19.1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=wc-lnxnode-c,kubernetes.io/os=linux
wc-mster-c Ready master 2d v1.19.0 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/arch=amd64,kubernetes.io/hostname=wc-mster-c,kubernetes.io/os=linux,node-role.kubernetes.io/master=
wc-winnode-c Ready 4h16m v1.19.0 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=windows,kubernetes.io/arch=amd64,kubernetes.io/hostname=wc-winnode-c,kubernetes.io/os=windows,node.kubernetes.io/windows-build=10.0.17763
kubectl get po
NAME READY STATUS RESTARTS AGE
nginx-c100-845597d757-vhpm8 1/1 Running 0 177m
win-webserver-c1000-568df4cb6d-q77fq 0/1 ContainerCreating 0 12m
But I’m struggling with the error when I’m creating windows pod.
kubectl describe said,
Events:
Type Reason Age From Message
Normal Scheduled 20s Successfully assigned default/win-webserver-c1000-568df4cb6d-q77fq to wc-winnode-c
Warning FailedCreatePodSandBox 18s kubelet, wc-winnode-c Failed to create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container “31b6f1a67ab57edd6df5e834d182eab441b5c8e566903005469e47a6e3896764” network for pod “win-webserver-c1000-568df4cb6d-q77fq”: networkPlugin cni failed to set up pod “win-webserver-c1000-568df4cb6d-q77fq_default” network: CreateFile C:\CalicoWindows\libs\calico…\nodename: The system cannot find the file specified.: check that the calico/node container is running and has mounted /var/lib/calico/, failed to clean up sandbox container “31b6f1a67ab57edd6df5e834d182eab441b5c8e566903005469e47a6e3896764” network for pod “win-webserver-c1000-568df4cb6d-q77fq”: networkPlugin cni failed to teardown pod “win-webserver-c1000-568df4cb6d-q77fq_default” network: CreateFile C:\CalicoWindows\libs\calico…\nodename: The system cannot find the file specified.: check that the calico/node container is running and has mounted /var/lib/calico/]
Normal SandboxChanged 6s (x2 over 17s) kubelet, wc-winnode-c Pod sandbox changed, it will be killed and re-created.
kubelet, kube-proxy, CalicoNode, CalicoFelix service is running fine and kubelet and calico doesn’t have specific errors.
PS C:\CalicoWindows\logs> dir
Directory: C:\CalicoWindows\logs
Mode LastWriteTime Length Name
-a---- 2020-09-11 오후 2:42 0 calico-felix.err.log
-a---- 2020-09-11 오후 2:42 237 calico-felix.log
-a---- 2020-09-11 오후 2:42 0 calico-node.err.log
-a---- 2020-09-11 오후 2:42 19034 calico-node.log
Is that possible for using self managed on-prem kuberentes with windows workernode?
My windows server is 2019(1809). is that possible to using calico on windows with this version?
…And is there any suggestion to solve this out?
Many thanks.