freezing-action-16232
05/16/2023, 7:39 PMfast-garage-66093
05/16/2023, 8:00 PMfreezing-action-16232
05/16/2023, 8:00 PMfast-garage-66093
05/16/2023, 8:01 PMfreezing-action-16232
05/16/2023, 8:02 PMfast-garage-66093
05/16/2023, 8:12 PMK3S_EXEC
in /etc/environment
inside the VM. I don't know if this will work after k3s has already been initialized, so getting the value in there may be complicated. It should work via provisioning script, but it may need to be put in place directly after doing a factory reset.K3S_EXEC=--cluster-cidr "172.31.0.0/24" --service-cidr "172.31.1.0/24" --cluster-dns "172.31.1.10"
10.42.0.0/16
or 10.43.0.0/16
subnets. If it wasn't, then I'm looking at the wrong settings...freezing-action-16232
05/16/2023, 8:19 PMfast-garage-66093
05/16/2023, 8:25 PMcalm-sugar-3169
05/16/2023, 10:13 PM--cluster-cidr
via provisioning scripts to define the cluster subnet you are looking for. Could the conflicting ip address come from a service/cluster (definition manifest)?fast-garage-66093
05/16/2023, 10:23 PM172.30.186.63
is more likely the WSL ethernet address than something inside the clustercalm-sugar-3169
05/16/2023, 10:32 PMfast-garage-66093
05/16/2023, 10:33 PMfreezing-action-16232
05/17/2023, 6:32 AMwide-mechanic-33041
05/17/2023, 11:20 AM