Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
f
freezing-action-16232
05/16/2023, 7:39 PMHello guys, currently the kubernetes cluster gets configured with an ip address which interferes with a machine in our network. Is it possible to change the subnet over which the ip addresses are generated?
f
fast-garage-66093
05/16/2023, 8:00 PMWindows, macOS, or Linux? If macOS, using admin mode to get bridged network? What is the conflicting subnet range?
f
freezing-action-16232
05/16/2023, 8:00 PMWindows 10 Pro
f
fast-garage-66093
05/16/2023, 8:01 PM@calm-sugar-3169 Any idea?
f
freezing-action-16232
05/16/2023, 8:02 PMbasically the network guys said we have to narrow down the ip addresses to this subnet - 172.31.0.0/16
f
fast-garage-66093
05/16/2023, 8:12 PMOk, this is going to be a bit tricky, and I don't have time today to test it, but basic idea is to set the network ranges with "k3s server" parameters via
K3S_EXEC/etc/environmentThe options can be found at https://docs.k3s.io/cli/server#networking
So you will need something like
K3S_EXEC=--cluster-cidr "172.31.0.0/24" --service-cidr "172.31.1.0/24" --cluster-dns "172.31.1.10"Or split the available network space into larger subnets if you expect to have mode pod/service, but I guess that is unlikely in a desktop setup 🙂
Anyways, I expect this will require a fair amount of experimentation to get it to work. Maybe @curved-zebra-30454 will be able to help with it
Please confirm that the conflicting IP address was in the
10.42.0.0/1610.43.0.0/16f
freezing-action-16232
05/16/2023, 8:19 PM172.30.186.63
this was the conflicting ip address
f
fast-garage-66093
05/16/2023, 8:25 PMOk, so then it is not the cluster or server subnets that are the problem. Let's wait until @calm-sugar-3169 is back and see if he has suggestions
c
calm-sugar-3169
05/16/2023, 10:13 PMAs per Jan’s suggestion up above, looking at here: https://github.com/rancher-sandbox/rancher-desktop/blob/main/pkg/rancher-desktop/assets/scripts/service-k3s.initd#L62 it looks like you can provide the
--cluster-cidrf
fast-garage-66093
05/16/2023, 10:23 PM@calm-sugar-3169 I think
172.30.186.63@freezing-action-16232 Where did this address come from?
What was it used for?
c
calm-sugar-3169
05/16/2023, 10:32 PMIt’s highly possible that is an IP address that belongs to the wsl network, I just don’t have enough context on what is the user experiencing and what kind of errors are they seeing. If the wsl address is in conflict with “one of the machine in our network” I don’t think they can even get to deploying a cluster.
f
fast-garage-66093
05/16/2023, 10:33 PMYeah, there is not much we can do unless we know what the address was used for
f
freezing-action-16232
05/17/2023, 6:32 AMThis address is the kubernetes server address, the one that sits in the .kube/config
So yes, this is all related with the subnet that the WSL gets configured
I was able to solve the problem by editing two values in the registry which essentially configure the subnet for the WSL
w
wide-mechanic-33041
05/17/2023, 11:20 AMyeah thats the odd part for me. the cluster shouldn’t be exposed to the host. The WSL elected subnet is, but it is supposed to test the routeability of the subnet it chooses which it sounds like it did a poor job with.