#Trident Operator - Multi Home Support

1 messages · Page 1 of 1 (latest)

unborn cave
#

Hi,

we are currently using the Trident Operator with ontap-nas driver in a customers Openshift cluster and everything works fine.

The customer would like to attach a second NIC to his Openshift cluster to access the data LIF over a network that supports bigger MTU size (9000).

Our idea would be:

  • Add a second interface to the Openshift node with a static IP (using nmstate operator)
  • Configure the corresponding route to the data LIF on this NIC

Questions that arise?

  • Do you see any blocker?
    • I can imagine that we might have to overwrite the export policy, as Trident might not be aware of the second NIC IP.
  • Is this officially supported by Netapp and can be recommended to our customer?
  • Any other ideas on how we can solve this?

Thanks and BR,

Philipp

iron heron
#

If you put the second NIC into a different layer 2 network (VLAN) then you don't need a static route. This is much less trouble (speaking from my own experience here) than having a node with two NICs in the same Network. That always spells trouble

unborn cave
#

Of course you are right, no need for a static route. And yes of course it would be a dedicated layer 2 network (VLAN) for data access.

So this would be officially an officially supported scenario by Netapp Trident?

I am going to do a test and post the results here.