Configure Kubernetes on dedicated NIC

[saschagrau]

Hello all together,

i want to setup a dedicated NIC for the Kubernetes Node and can not find a useful documentation for that.
That's what i already tried:

NIC 1 -> 10.10.10.250 (also configured as the TrueNAS Web UI ip)
NIC 2 -> 10.10.40.250 (configured as Kubernetes NodeIP)

Kubernetes
NodeIP : 10.10.40.250
Route v4 interface: NIC2
Route v4 gateway: 10.10.40.1

After installing an app from TrueCharts (Plex) i can ping the IP and can make a port test, but i can not open the Web UI.

PS C:\> ping 10.10.40.250

Pinging 10.10.40.250 with 32 bytes of data:
Reply from 10.10.40.250: bytes=32 time<1ms TTL=64
...
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

PS C:\> tnc 10.10.40.250 -port 32400

ComputerName : 10.10.40.250
RemoteAddress : 10.10.40.250
RemotePort : 32400
InterfaceAlias : Ethernet
SourceAddress : 10.10.10.203
TcpTestSucceeded : True

Do i missed some settings here, or is there a documentation on setting up that correctly?

Regards,
Sascha Grau

TrueNAS-SCALE-22.02.1

 

[somewhatdamaged]

Very keen on understanding this as well.... I can't find anything on Google thats useful, and i tried searching this forum too

 

[NugentS]

I tried this, and gave up. Basically you can't at the moment

 

[DaSnipe]

I’m confused, I’m using Kubernetes on a second NIC and can ping/access all my apps. Did you create Plex after setting everything to the second NIC?

 

[NugentS]

@DaSnipe - are the containers still available on the first NIC as well? I am more than happy to be wrong - ecstatic even

 

[DaSnipe]

No. Only on the 2nd NIC. I set that up before installing any apps though. Both my NIC can access web GUI (I left it to default 0.0.0.0) but set Kubernetes to 192.168.88.100 (my 10gb static IP)

 

[somewhatdamaged]

Could you perhaps share some of your configuration?

As an example, my main NIC is 192.168.10.252, and i set up a second with 192.168.11.252 but when i try and switch the kubernetes over to the second NIC, it just crashes (and are you able to leave the same gateway?)

 

[DaSnipe]

Could you perhaps share some of your configuration?

As an example, my main NIC is 192.168.10.252, and i set up a second with 192.168.11.252 but when i try and switch the kubernetes over to the second NIC, it just crashes (and are you able to leave the same gateway?)

Changing an existing kubernetes node to the second NIC would do that. I guess you can try to backup and restore your apps and see if it picks up the 2nd NIC. I started fresh on my second NIC (installing apps), I only used the first NIC (which is still using DHCP) to find my TrueNAS box and set the static IP for my 2nd NIC

 

[somewhatdamaged]

Thanks man. I'll give that a try and see what happens...!

 

[PackElend]

hey there,
looks like Kubernetes and a dedicated network interface is not an easy thing.

This is my lab decice. To keep things simialr between producitve and lab, it as single NIC bond
I want chart apps are only available within a single VLAN (VLAN999) in my case.
br8 is gets IP by DHCP as it shall be my GUI access (things are set by Router, less to mess up with).

looks like Kubernetes Node IP can only be a static IP, so I set

but I can reach Pi Hole on

1. http://10.10.8.9:20720/
2. http://10.10.9.231:20720/

Moreover, pi-hole sees only interface on TN plus router Gateway, not the VMs on TN or other clients in same VLAN

Code:

PS C:\Users\me> tnc 10.10.8.9 -port 20720
ComputerName     : 10.10.8.9
RemoteAddress    : 10.10.8.9
RemotePort       : 20720
InterfaceAlias   : LAN DELL SCREEN
SourceAddress    : 10.10.20.85
TcpTestSucceeded : True


PS C:\Users\me> tnc 10.10.8.9 -port 20720
ComputerName     : 10.10.8.9
RemoteAddress    : 10.10.8.9
RemotePort       : 20720
InterfaceAlias   : LAN DELL SCREEN
SourceAddress    : 10.10.20.85
TcpTestSucceeded : True

So I'm wondering, is it feasible at all?