freezing-action-1623205/16/2023, 7:39 PM
fast-garage-6609305/16/2023, 8:00 PM
freezing-action-1623205/16/2023, 8:00 PM
fast-garage-6609305/16/2023, 8:01 PM
freezing-action-1623205/16/2023, 8:02 PM
fast-garage-6609305/16/2023, 8:12 PM
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"
subnets. If it wasn't, then I'm looking at the wrong settings...
freezing-action-1623205/16/2023, 8:19 PM
fast-garage-6609305/16/2023, 8:25 PM
calm-sugar-316905/16/2023, 10:13 PM
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-6609305/16/2023, 10:23 PM
is more likely the WSL ethernet address than something inside the cluster
calm-sugar-316905/16/2023, 10:32 PM
fast-garage-6609305/16/2023, 10:33 PM
freezing-action-1623205/17/2023, 6:32 AM
wide-mechanic-3304105/17/2023, 11:20 AM