Skip to main content
A newer release of this product is available.

Configure an ONTAP NAS backend

Contributors juliantap
PDFs

Learn about configuring an ONTAP backend with ONTAP and Cloud Volumes ONTAP NAS drivers.

Warning Customers must use the ontap-nas driver for production workloads that require data protection, disaster recovery, and mobility. Astra Control provides seamless protection, disaster recovery, and mobility for volumes created with the ontap-nas driver. The ontap-nas-economy driver should be used only in limited use cases where anticipated volume usage is expected to be much higher than what ONTAP supports, with no anticipated data protection, disaster recovery, or mobility (moving volumes between Kubernetes clusters) requirements.

User permissions

Astra 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, Astra 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.

Note If you use the limitAggregateUsage parameter, cluster admin permissions are required. When using Amazon FSx for NetApp ONTAP with Astra 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.