ONTAP SAN driver overview
Learn about configuring an ONTAP backend with ONTAP and Cloud Volumes ONTAP SAN drivers.
ONTAP SAN driver details
Trident provides the following SAN storage drivers to communicate with the ONTAP cluster. Supported access modes are: ReadWriteOnce (RWO), ReadOnlyMany (ROX), ReadWriteMany (RWX), ReadWriteOncePod (RWOP).
Driver | Protocol | volumeMode | Access modes supported | File systems supported |
---|---|---|---|---|
|
iSCSI |
Block |
RWO, ROX, RWX, RWOP |
No filesystem; raw block device |
|
iSCSI |
Filesystem |
RWO, RWOP ROX and RWX are not available in Filesystem volume mode. |
|
|
NVMe/TCP Refer to Additional considerations for NVMe/TCP. |
Block |
RWO, ROX, RWX, RWOP |
No filesystem; raw block device |
|
NVMe/TCP Refer to Additional considerations for NVMe/TCP. |
Filesystem |
RWO, RWOP ROX and RWX are not available in Filesystem volume mode. |
|
|
iSCSI |
Block |
RWO, ROX, RWX, RWOP |
No filesystem; raw block device |
|
iSCSI |
Filesystem |
RWO, RWOP ROX and RWX are not available in Filesystem volume mode. |
|
|
User permissions
Trident expects to be run as either an ONTAP or SVM administrator, typically using the admin
cluster user or a vsadmin
SVM user, or a user with a different name that has the same role. For Amazon FSx for NetApp ONTAP deployments, Trident expects to be run as either an ONTAP or SVM administrator, using the cluster fsxadmin
user or a vsadmin
SVM user, or a user with a different name that has the same role. The fsxadmin
user is a limited replacement for the cluster admin user.
If you use the limitAggregateUsage parameter, cluster admin permissions are required. When using Amazon FSx for NetApp ONTAP with Trident, the limitAggregateUsage parameter will not work with the vsadmin and fsxadmin user accounts. The configuration operation will fail if you specify this parameter.
|
While it is possible to create a more restrictive role within ONTAP that a Trident driver can use, we don't recommend it. Most new releases of Trident will call additional APIs that would have to be accounted for, making upgrades difficult and error-prone.
Additional considerations for NVMe/TCP
Trident supports the non-volatile memory express (NVMe) protocol using the ontap-san
driver including:
-
IPv6
-
Snapshots and clones of NVMe volumes
-
Resizing an NVMe volume
-
Importing an NVMe volume that was created outside of Trident so that its lifecycle can be managed by Trident
-
NVMe-native multipathing
-
Graceful or ungraceful shutdown of the K8s nodes (24.06)
Trident does not support:
-
DH-HMAC-CHAP that is supported by natively by NVMe
-
Device mapper (DM) multipathing
-
LUKS encryption