Open paraddise opened 1 week ago
Found workaround
ib0
via `linstor n i create LinstorSatelliteConfiguration
and adding PrefNic=ib0
Now, I'm searching the way to automate this at node registration at linstor.
Maybe there are plans to add Interfaces in LinstorSatelliteConfiguration
?
Currently, the Operator is the one registering the Satellites. So it can only really use what Kubernetes exposes on the Pod (perhaps also on the K8s Node resource). So we would need a way to expose the IP address of this secondary interface to Kubernetes, and then a way for the Operator to pick up this information.
You could probably somehow coble together an initContainer
using the LinstorSatelliteConfiguration.spec.podTemplate
that scans the output of ip addr show dev ...
and registers that interface on Pod startup.
I haven't thought about patches, thank you, will try it
I have kubernetes node with 2 interfaces, 1 for use with kubernets, another is infiniband interface for drbd traffic only. I have external linstor controller and piraes deployed to kubernetes. Currently piraeus when creating satellite in controller takes ip from
status.nodeIPs
of Pod. So I can't change IP address of registered satellite. I propose to create field in LinstorSatelliteConfiguration where you can pass interface name or IP address of sattelite that will be created.