icy-garage-31078
09/23/2022, 4:07 PMfast-garage-66093
09/23/2022, 4:12 PMicy-garage-31078
09/23/2022, 4:12 PMfast-garage-66093
09/23/2022, 4:13 PMicy-garage-31078
09/23/2022, 4:20 PMwatch kubectl get pod
). After that failed, I setup a new VM using ubuntu server using the 'lightweight' install and went with their self installed version of microk8s. When I connected to this instead, the errors have gone away on both my personal and work laptops. The only issue I'm having now is that running the afore mentioned command is extremely slow when I'm connected to the vpn on my work laptop. Once I disconnect, it seems to be running fine. I was thinking if possible, I'd like to try using this same style 'setup' via rancher-desktop to see if this takes care of the rest of my issues.fast-garage-66093
09/23/2022, 4:51 PMicy-garage-31078
09/23/2022, 5:02 PMwatch kubectl get pod
directly on the machine and continued to have the every couple seconds I would get the TCP Timeouts, even though I was directly on the machine at that point (so shouldn't of been any TCP connections across the network). Using ubuntu w/microk8s is working like a charm so long as I'm not trying to do host mounts and the vpn is disabled.fast-garage-66093
09/23/2022, 5:09 PMicy-garage-31078
09/23/2022, 5:11 PMfast-garage-66093
09/23/2022, 5:12 PMicy-garage-31078
09/23/2022, 5:13 PMfast-garage-66093
09/23/2022, 5:15 PMicy-garage-31078
09/23/2022, 5:16 PMfast-garage-66093
09/23/2022, 5:16 PMk3s
and a k8s
template, the later using kubeadm
limactl start --list-templates
shows you the installed templates, and you can create a VM with e.g. limactl start <template://k8s>