brando56894
Wizard
- Joined
- Feb 15, 2014
- Messages
- 1,537
Edit: seems like this is a known issue when switching between the beta and the nightlies. I opened this ticket Nuking my the ix-applications dataset when on the nightlies fixed everything.
I just want to make sure I have this setup correctly because ever since I switched from Arch w/OpenZFS to TrueNAS SCALE I've been having networking issues, largely because I have everything setup differently.
Config
My intention is to have each NIC connected to a different subnet
I have static IPs setup under Network -> Interfaces and have the routes and DNS servers added under Global Configurations. I can ping both gateways from truenas itself and from an external host.
Problem
My k3s deployments always have networking issues, initially they're listening on both IPs and the settings under Apps -> Settings - Advanced Settings weren't populating so I couldn't set it to 192.168.3.7, I figured out how to manually set it by editing ix-applications/config.json and rebooting. This seemed to work as apps were available on 3.7 but then I deployed Traefik and had it listen on 80 and 443 instead of 9080 and 9443, and that somehow ended up killing the webui.
I was unable to fix it, and after a clean install of the most recent beta build I noticed that the fields under advanced settings were now populated, but shortly after starting up K3S the webui and everything under 1.7 became inaccessible. I reinstalled the beta and deleted the ix-aplications dataset so I could start fresh. I set it up as above, and then deployed everything and they all came up and were accessible with no issues.
I just did a manual upgrade to TrueNAS-SCALE-21.09-MASTER-20210914-092923 and now only two of my deployments are up: nzbget and plex, all others are stuck at deploying citing that the network isn't ready.
I have no idea what the issue is here....
I just want to make sure I have this setup correctly because ever since I switched from Arch w/OpenZFS to TrueNAS SCALE I've been having networking issues, largely because I have everything setup differently.
Config
My intention is to have each NIC connected to a different subnet
- enp9s0f1 is assigned 192.168.1.7 and is the management NIC for the UI, ssh and everything else.
- enp9s0f0 is assigned 192.168.3.7 and is used solely for Kubernetes
I have static IPs setup under Network -> Interfaces and have the routes and DNS servers added under Global Configurations. I can ping both gateways from truenas itself and from an external host.
Problem
My k3s deployments always have networking issues, initially they're listening on both IPs and the settings under Apps -> Settings - Advanced Settings weren't populating so I couldn't set it to 192.168.3.7, I figured out how to manually set it by editing ix-applications/config.json and rebooting. This seemed to work as apps were available on 3.7 but then I deployed Traefik and had it listen on 80 and 443 instead of 9080 and 9443, and that somehow ended up killing the webui.
I was unable to fix it, and after a clean install of the most recent beta build I noticed that the fields under advanced settings were now populated, but shortly after starting up K3S the webui and everything under 1.7 became inaccessible. I reinstalled the beta and deleted the ix-aplications dataset so I could start fresh. I set it up as above, and then deployed everything and they all came up and were accessible with no issues.
I just did a manual upgrade to TrueNAS-SCALE-21.09-MASTER-20210914-092923 and now only two of my deployments are up: nzbget and plex, all others are stuck at deploying citing that the network isn't ready.
I have no idea what the issue is here....
Last edited:
