Kubernete start on wrong interface

[JenJen]

Hi,

Today I reboot the NAS and the app won't deploy.
This is my NAS version: TrueNAS-SCALE-22.02.4

I began to use truenas scale in 2021 and I never had any problem on this.

I had 2 NIC in my NAS and I use both (one for the VM and the other for the NAS GUI and kubernete):

This is the config where the app won't deploy (sometimes I had docker is not runing and sometimes in the app log :"0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/unreachable: }, that the pod didn't tolerate."):

This is the config where the app deploy:

But all my app are accessible on 192.168.1.17... It's my second NIC and I configure my interface to be on 192.168.1.151.
I don't understand why all my app start on the second NIC. I never had any problem on it and I don't understand what is my configuration mistake.

I unset pool and set again, I reboot several times.

 

[JenJen]

After X reboot, finally all my app start on the 192.168.1.151.

I think I will delete the second NIC and use a bridge, to avoid this behaviour.