SOLVED K3s: default route configured, but error "not present on any cidr used by the system"

[guillheu]

Hi.
After setting the default route for my k3s, I still get the following error :

Code:

kubernetes.route_v4_gateway: Specified value is not present on any network cidr in use by the system

However, the k3s gateway is set to 192.168.1.1, and I have a NIC with address 192.168.1.21/24.

I've had this issue before on another consumer grade bare-metal system which had a single NIC. However, another deployment on a VM worked without problems. Any idea what's causing this ? Did I just miss something obvious ?

 

[sretalla]

netstat -r

 

[guillheu]

netstat -r

 

[sretalla]

And have you set that in Network | Global Configuration too? (as suggested in the message)

 

[guillheu]

And have you set that in Network | Global Configuration too? (as suggested in the message)

The IPv4 default route is set to 192.168.1.1 in the global network configuration

 

[sretalla]

OK; and what about setting the Node IP to 192.168.1.21 ?

 

[guillheu]

OK; and what about setting the Node IP to 192.168.1.21 ?

Doesn't seem like I can do that from the UI. Only option I get is 0.0.0.0.

 

[sretalla]

OK, so maybe that's pointing us in a direction...

Have you set that IP address as static?

Maybe also time to consider using a Bridge to do the networking properly while you're there.

Accessing NAS From a VM

Provides instructions on how to create a bridge interface for the VM and provides Linux and Windows examples.

www.truenas.com

 

[guillheu]

OK, so maybe that's pointing us in a direction...

Have you set that IP address as static?

Maybe also time to consider using a Bridge to do the networking properly while you're there.

Accessing NAS From a VM

Provides instructions on how to create a bridge interface for the VM and provides Linux and Windows examples.

www.truenas.com

I set up a bridge interface like you recommended, then set that bridge interface as my k3s interface and it worked. Thank you!
I'm still confused as to why I had to do all this on my bare-metal system, but not on the TrueNAS test VM I'm running on my desktop. Any ideas ?

Marking as solved.

 

[sretalla]

why I had to do all this on my bare-metal system, but not on the TrueNAS test VM I'm running on my desktop. Any ideas ?

Not sure, but may be related to the virtual NIC and how it was bridged/configured and which driver it used.

Anyway, glad you got it working how you wanted.