Add note on requirements for parallel operation of Trident and EBS-CSI

Page URL

https://docs.netapp.com/us-en/trident/trident-use/trident-fsx-prep.html

Page title

Integrate Amazon FSx for NetApp ONTAP

Summary

The standard Trident worker node prep steps for iSCSI guide users to enable multipathing for iSCSI. Unfortunately this breaks integration with EBS disks and the EBS-CSI driver, as the EBS disks cannot be attached once multipathing is enabled. The solution is to blacklist EBS disks in the multipath config. See https://github.com/kubernetes-sigs/aws-ebs-csi-driver/issues/1417 for additional details.

Can we please add a note about this to the docs? I'd suggest the following, either as a new chapter or within the Requirements chapter:

Parallel usage of Trident SAN/iSCSI and EBS-CSI driver

If you intend to use Trident ontap-san drivers (e.g. iSCSI), the required multipathing setup on the nodes can break the EBS CSI driver. In order to enable multipathing without impacting EBS disks on the same node, the Elastic Block Store needs to be blacklisted in your multipathing configuration. The following is an example of a multipath.conf that makes the required settings for Trident and blacklists EBS disks from multipathing:

defaults {
    find_multipaths no
}
blacklist {
    device {
        vendor "NVME"
        product "Amazon Elastic Block Store"
    }
}

Public issues must not contain sensitive information

[X] This issue contains no sensitive information.

NetAppDocs / trident