https://rancher.com/ logo
Join Slack
Powered by
I am using rancher desktop version 1.18.2, My comp...
# rancher-desktop
l
I am using rancher desktop version 1.18.2, My company has some limitation on using ip address range , how do I tweak rancher desktop CIDR to use my ip address range ?
w
you mean in the VM? are you on mac or windows?
l
I mean POD, service etc.. I am on Windows. I want rancher desktop to use the range of IP what is permitted on my network
w
well you set the IPs on ingress?
what are you using for ingress in this case?
l
In rancher kubernetes cluster.. my pods are not even able to communicate because looks like company network layer is not allowing it.. one of the pod is allocated with ip of 10.42.0.245 which is the default in rancher desktop but it is not permitted on my corporate network.. BTW, I am using ngin-ingress
w
so are you talking rancher or rancher desktop?
l
rancher desktop
w
the pod routing would be all internal to the VM on RD
now ingress from external or host would be different
so on windows you need ot make sure the WSL virtual interface isn't getting stomped on
l
ok thanks, what to check on the WSL layer ?
w
gets a bit spicy as WSL tests the private CIDRs before selecting the one that it will use for the host veth https://learn.microsoft.com/en-us/windows/wsl/networking#default-networking-mode-nat
you can look at your 
route print
results and find the WSL interface from like a 
ipconfig /all
to make sure the gateway didn't get modified by your VPN or something
if the 10/8 is routeable than a bit surprised WSL would have used that for its range
l
sorry addtional clarification, if the pod routing would be all internal to the VM on RD, then why my processes which needs to connect with each other running in pod within RD, are failing ?
w
your app so hard to know, but its a single node so all traffic would be inside the VM
l
Thanks for your inputs. I'll investigate using the links you provided
5 Views
Open in Slack
PreviousNext
Powered by