2

In AWS, I have created a RKE2 cluster using the Rancher 2.6.2 UI.
There are two Ubuntu 20.04 control plane nodes, and pods on these hosts can reach other pods/ the internet.
My Windows node (Server 2019, 1809 Datacenter) joins the cluster without any issues, however, the Windows containers cannot seem to reach any other network with curl or ping.

Checking the process that RKE2 uses:

Get-Process -Name rke2,containerd,calico-node,kube-proxy,kubelet  

Calico-Node is not running. I checked event viewer for the RKE2 application logs and found:

Felix exited: exit status 129  

Is there somewhere to check for more detailed logs? RKE2 seems to have things moved around, and it doesn't line up with the Calico docs.

I have disabled source/dest checks on the network interfaces of all of the Kubernetes nodes in AWS.
I also created a Windows firewall rule to allow Kubelet on 10250.

Mike
  • 21
  • 1

0 Answers0