Restrict Longhorn storage traffic to specific interface or IP address? #13198
-
|
Howdy. I've just added a second interface to my nodes to dedicate to a cluster-only SAN. The interface is 2.5Gps Ethernet. These interfaces will be connected to a dedicated 2.5Gps Ethernet switch. I also have a dedicated NVME in each node for data storage. I'd like to limit traffic for Longhorn storage to only flow over the 2.5Gbps interface or associated assigned IP. Has anyone created this scenario? What's the best approach? I checked the Talos and Longhorn docs and didn't see anything specifically relevant. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Talos can't control how Longhorn operates, you can assign addresses to the links, routes. You can force kubelet's node IP to be that dedicated interface IP, so that all pod traffic flows there, but besides that it's in Longhorn's hand how to route things. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. I'll look deeper at Longhorn's options. |
Beta Was this translation helpful? Give feedback.
Talos can't control how Longhorn operates, you can assign addresses to the links, routes.
You can force kubelet's node IP to be that dedicated interface IP, so that all pod traffic flows there, but besides that it's in Longhorn's hand how to route things.