TrueNas Scale K8S cluster IP's seems to be conflicting with local range

[georgelza]

Hi all, seem to have run into a issue.
my entire local range came from before Scale, before the K8S cluster was around.
172.16.10.0/24 my NAS sits on 172.16.10.24 and various of the services sit on this range, like plex on 172.16.10.26
172.16.20.0/24 Wifi devices
172.16.100.0/24 smart home devices

I just upgraded from Bluefin to TrueNAS-SCALE-23.10.2
My apps seem to be stuck in deploying phase, and well the TrueChart guys are wanting yo rip me a new a hole for using 172.16.0.0 locally. well that is what it is... my house range is and has been like thet for 5 yrs, with over 100 smart devices on it so can't reconfigure that side.
is there a way to tell the K8 / container environment to live on something else.

See below for 2 sets of logs I got.

2024-03-03 13:57:25.716277+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/50413" 2024-03-03 13:57:25.716314+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "127.0.0.1". Port: "UDP/50413" 2024-03-03 13:57:25.716323+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "172.17.0.81". Port: "TCP/50413" 2024-03-03 13:57:25.716333+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "172.17.0.81". Port: "UDP/50413" 2024-03-03 13:57:25.716345+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "::1". Port: "TCP/50413" 2024-03-03 13:57:25.716358+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "::1". Port: "UDP/50413" 2024-03-03 13:57:25.716365+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "fe80::3ce5:48ff:fed0:e825%eth0". Port: "TCP/50413" 2024-03-03 13:57:25.716372+02:00(I) 2024-03-03T13:57:25 - Successfully listening on IP. IP: "fe80::3ce5:48ff:fed0:e825%eth0". Port: "UDP/50413"

my plex server, all my network management tools, they all on the apps. The K8S settings... not sure why this is then conflicting with my local 172.16.0.0 ranges that service CIDR should be remapped by metallb to 172.16.10.0 range.

G

 

[danb35]

is there a way to tell the K8 / container environment to live on something else.

Of course there is. Apps -> Settings -> Advanced Settings. You can change cluster CIDR, Service CIDR, and the DNS IP there. But apparently that will result in loss of all your apps and data, so you'll need to reinstall them.

the TrueChart guys are wanting yo rip me a new a hole for using 172.16.0.0 locally

It's certainly a valid private IP range, but it's kind of interesting how rarely it's used--just about everyone seems to use either 192.168.0.0 or 10.0.0.0.

 

[georgelza]

Of course there is. Apps -> Settings -> Advanced Settings. You can change cluster CIDR, Service CIDR, and the DNS IP there. But apparently that will result in loss of all your apps and data, so you'll need to reinstall them.

It's certainly a valid private IP range, but it's kind of interesting how rarely it's used--just about everyone seems to use either 192.168.0.0 or 10.0.0.0.

hi there

ye 172.16.0.0 is a more than supported private range... and ye 192.168.0.0 is also... but everyone knows the latter, including our friendly hackers, so not being on it, it's not the end all of security, but it helps a bit.

I can't afford to change the K8s environment, 172.17.0.0 s as you said that all nuke my apps and well thats not a option.
trying to figure out how metallb-config that accepts my 172.16.10.10-172.16.10.100 and well the cluster seems to sit on 172.17.0.0
some how need to get metallb to start up/run and listen on 172.16.10.0 and route to 172.18.0.0

tried asking for help on truecharts but ye.. got more of a barking at due to ranges used that how to work around problem.

 

[georgelza]

plex seems to be running and it's saying it's listening on the desired address.
but some how it's not being routed into/onto it.

G

 

[georgelza]

can someone point me to how/where to open a support ticket,,, so far when i was stuck i always got helped/solution figured out here via discussing problem.

G

 

[georgelza]

... made some progress, uninstalled metallb and reinstalled it... it's running, but still not routing traffic onto my apps... trying the old Microsoft fix... reboot the NAS.

G