WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277
Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.
| # API server: nodes should be able to reach k3s server tcp port 6443 | |
| # flannel vxlan: udp port 8472 for nodes to communicate (server and agents) | |
| # metrics server: it collects resource metrics from kubelets and exposes them in k8s api server through metrics api. tcp port 10250 | |
| # https://rancher.com/docs/k3s/latest/en/installation/install-options/ | |
| # run the installation script | |
| curl -sfL https://get.k3s.io | sh - | |
| # create k3s group and add user to avoid using always sudo | |
| sudo groupadd k3s |
