IBM Cloud Docs
NetApp ONTAP-NAS

NetApp ONTAP-NAS

Set up NetApp ONTAP-NAS storage for IBM Cloud Satellite® clusters. You can use Satellite storage templates to create storage configurations. When you assign a storage configuration to your clusters, the storage drivers of the selected storage provider are installed in your cluster.

Before you can create storage configurations by using the NetApp NAS template, you must deploy the NetApp ONTAP-NAS template which installs the required operator.

Before you can deploy storage templates to clusters in your location, make sure you set up Satellite Config by selecting the Enable cluster admin access for Satellite Config option in the console or including the --enable-config-admin option when you create your cluster.

You cannot scope Satellite storage service to resource groups. However, if you are scoping other resources such as location and cluster to resource groups, you need to add Satellite reader and link administrator role for all resources in the account.

Prerequisites for NetApp ONTAP-NAS

  • You must configure your backend ONTAP cluster as a Trident backend.
  • You must have a dedicated Storage Virtual Machine (SVM) for Trident. Volumes created by Trident are created in this SVM.
  • You must have one or more aggregates assigned to the SVM. You can add aggregates with the netapp1::> vserver modify -vs <svm_name> -aggr-list <aggregate(s)_to_be_added> command.
  • You must configure permissions on the default export policy or create your own custom export policy.
  • You must have one or more dataLIFs for the SVM.
  • You must have NFS services enabled on the SVM.
  • You must set up a snapshot policy on the SVM.
  1. Create a Satellite location.

  2. Create a Satellite cluster.

    • Make sure that you select the Enable cluster admin access for Satellite Config option when you create the cluster. If you don't enable Administrator (admin) access for Satellite Config when creating your cluster, you must re-create your cluster and enable admin access before you can deploy storage.
    • Your cluster must meet the requirements for ONTAP-NAS. For more information, see the NetApp documentation.
    • Your hosts must meet the Satellite host requirements in addition to the requirements for ONTAP-NAS.
  3. Add your Satellite to a cluster group.

Creating and assigning a configuration in the console

  1. Review the parameter reference.

  2. From the Locations console, select the location where you want to create a storage configuration.

  3. Select Storage > Create storage configuration

  4. Enter a name for your configuration.

  5. Select the Storage type.

  6. Select the Version and click Next

  7. If the Storage type that you selected accepts custom parameters, enter them on the Parameters tab.

  8. If the Storage type that you selected requires secrets, enter them on the Secrets tab.

  9. On the Storage classes tab, review the storage classes that are deployed by the configuration or create a custom storage class.

  10. On the Assign to service tab, select the service that you want to assign your configuration to.

  11. Click Complete to assign your storage configuration.

Creating a configuration in the CLI

  1. Review the parameter reference for the template version that you want to use.

  2. Log in to the IBM Cloud CLI.

    ibmcloud login
    
  3. List your Satellite locations and note the Managed from column.

    ibmcloud sat location ls
    
  4. Target the Managed from region of your Satellite location. For example, for wdc target us-east. For more information, see Satellite regions.

    ibmcloud target -r us-east
    
  5. If you use a resource group other than default, target it.

    ibmcloud target -g <resource-group>
    
  6. Copy one of the following example command for the template version that you want to use. For more information about the command, see ibmcloud sat storage config create in the command reference.

    Example command to create a version 22.04 configuration.

    ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-ontap-nas --template-version 22.04 --param "managementLIF=MANAGEMENTLIF"  --param "dataLIF=DATALIF"  --param "svm=SVM"  --param "username=USERNAME"  --param "password=PASSWORD"  --param "exportPolicy=EXPORTPOLICY"  --param "limitVolumeSize=LIMITVOLUMESIZE"  --param "limitAggregateUsage=LIMITAGGREGATEUSAGE"  --param "nfsMountOptions=NFSMOUNTOPTIONS" 
    

    Example command to create a version 22.10 configuration.

    ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-ontap-nas --template-version 22.10 --param "managementLIF=MANAGEMENTLIF"  --param "dataLIF=DATALIF"  --param "svm=SVM"  --param "username=USERNAME"  --param "password=PASSWORD"  --param "exportPolicy=EXPORTPOLICY"  --param "limitVolumeSize=LIMITVOLUMESIZE"  --param "limitAggregateUsage=LIMITAGGREGATEUSAGE"  --param "nfsMountOptions=NFSMOUNTOPTIONS" 
    

    Example command to create a version 24.02 configuration.

    ibmcloud sat storage config create --location LOCATION --name NAME --template-name netapp-ontap-nas --template-version 24.02 --param "managementLIF=MANAGEMENTLIF"  --param "dataLIF=DATALIF"  --param "svm=SVM"  --param "username=USERNAME"  --param "password=PASSWORD"  --param "exportPolicy=EXPORTPOLICY"  --param "limitVolumeSize=LIMITVOLUMESIZE"  --param "limitAggregateUsage=LIMITAGGREGATEUSAGE"  --param "nfsMountOptions=NFSMOUNTOPTIONS" 
    
  7. Customize the command based on the settings that you want to use.

  8. Run the command to create a configuration.

  9. Verify your configuration was created.

    ibmcloud sat storage config get --config CONFIG
    

Creating a configuration in the API

  1. Generate an API key, then request a refresh token. For more information, see Generating an IBM Cloud IAM token by using an API key.

  2. Review the parameter reference for the template version that you want to use.

  3. Copy one of the following example requests and replace the variables that you want to use.

    Example request to create a version 22.04 configuration.

    curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"netapp-ontap-nas\", \"storage-template-version\": \"22.04\", \"update-assignments\": true, \"user-config-parameters\": { \"entry.name\": \"MANAGEMENTLIF\", { \"entry.name\": \"DATALIF\", { \"entry.name\": \"SVM\", { \"entry.name\": \"EXPORTPOLICY\", { \"entry.name\": \"LIMITVOLUMESIZE\", { \"entry.name\": \"LIMITAGGREGATEUSAGE\", { \"entry.name\": \"NFSMOUNTOPTIONS\",\"user-secret-parameters\": { \"entry.name\": \"USERNAME\",{ \"entry.name\": \"PASSWORD\",}
    

    Example request to create a version 22.10 configuration.

    curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"netapp-ontap-nas\", \"storage-template-version\": \"22.10\", \"update-assignments\": true, \"user-config-parameters\": { \"entry.name\": \"MANAGEMENTLIF\", { \"entry.name\": \"DATALIF\", { \"entry.name\": \"SVM\", { \"entry.name\": \"EXPORTPOLICY\", { \"entry.name\": \"LIMITVOLUMESIZE\", { \"entry.name\": \"LIMITAGGREGATEUSAGE\", { \"entry.name\": \"NFSMOUNTOPTIONS\",\"user-secret-parameters\": { \"entry.name\": \"USERNAME\",{ \"entry.name\": \"PASSWORD\",}
    

    Example request to create a version 24.02 configuration.

    curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ \"config-name\": \"string\", \"controller\": \"string\", \"storage-class-parameters\": [ { \"additionalProp1\": \"string\", \"additionalProp2\": \"string\", \"additionalProp3\": \"string\" } ], \"storage-template-name\": \"netapp-ontap-nas\", \"storage-template-version\": \"24.02\", \"update-assignments\": true, \"user-config-parameters\": { \"entry.name\": \"MANAGEMENTLIF\", { \"entry.name\": \"DATALIF\", { \"entry.name\": \"SVM\", { \"entry.name\": \"EXPORTPOLICY\", { \"entry.name\": \"LIMITVOLUMESIZE\", { \"entry.name\": \"LIMITAGGREGATEUSAGE\", { \"entry.name\": \"NFSMOUNTOPTIONS\",\"user-secret-parameters\": { \"entry.name\": \"USERNAME\",{ \"entry.name\": \"PASSWORD\",}
    
  4. Verify that your storage configuration is created.

    ibmcloud sat storage config get --config <config>
    

Creating a storage assignment in the console

If you didn't assign your configuration to a cluster or service when you created it, you can create an assignment by completing the following steps.

  1. Open the Satellite console in your browser.
  2. Select the location where you created your storage configuration.
  3. Click the Locations tab, then click Storage.
  4. Click the storage configuration that you want to assign to a cluster group.
  5. On the Configuration details page, click Create storage assignment.
  6. In the Create an assignment pane, enter a name for your assignment.
  7. From the Version drop-down list, select the storage configuration version that you want to assign.
  8. Click Create to create the assignment.
  9. Verify that your storage configuration is deployed to your cluster.
    1. From the Satellite console, navigate to your Location and select Storage
    2. Click the storage configuration that you created and review the Assignments tab.
    3. Click the Assignment that you created and review the Rollout status for your configuration.

Creating an assignment in the CLI

  1. List your storage configurations and make a note of the storage configuration that you want to assign to your clusters.

    ibmcloud sat storage config ls
    
  2. Get the ID of the cluster, cluster group, or service that you want to assign storage to.

    To make sure that your cluster is registered with Satellite Config or to create groups, see Setting up clusters to use with Satellite Config.

    Example command to list cluster groups.

    ibmcloud sat group ls
    

    Example command to list clusters.

    ibmcloud oc cluster ls --provider satellite
    

    Example command to list Satellite services.

    ibmcloud sat service ls --location <location>
    
  3. Assign your storage configuration to the cluster, group, or service that you retrieved earlier. For more information, see the ibmcloud sat storage assignment create command.

    Example command to assign a configuration to a cluster group.

    ibmcloud sat storage assignment create --group GROUP --config CONFIG --name NAME
    

    Example command to assign a configuration to a cluster.

    ibmcloud sat storage assignment create --cluster CLUSTER --config CONFIG --name NAME
    

    Example command to assign a configuration to a service cluster.

    ibmcloud sat storage assignment create --service-cluster-id CLUSTER --config CONFIG --name NAME
    
  4. Verify that your assignment is created.

    ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
    

Creating a storage assignment in the API

  1. Copy one of the following example requests.

    Example request to assign a configuration to a cluster.

    curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignmentByCluster" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"channelName\": \"CONFIGURATION-NAME\", \"cluster\": \"CLUSTER-ID\", \"controller\": \"LOCATION-ID\", \"name\": \"ASSIGNMENT-NAME\"}"
    

    Example request to assign configuration to a cluster group.

    curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"channelName\": \"CONFIGURATION-NAME\", \"cluster\": \"string\", \"groups\": [ \"CLUSTER-GROUP\" ], \"name\": \"ASSIGNMENT-NAME\"}"
    
  2. Replace the variables with your details and run the request.

  3. Verify the assignment was created by listing your assignments.

    curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignments" -H "accept: application/json" -H "Authorization: Bearer TOKEN"
    

Updating storage assignments in the console

You can use the Satellite console to apply the latest patch updates to your assignments.

  1. From the Locations page in the Satellite console, select your location.

  2. Click the Storage tab to view your configurations.

  3. Click the configuration you want to update.

  4. Click information Information (i) icon to apply the latest revision or patch.

  5. Optional: Enable automatic patch updates for your storage assignment. Enabling automatic patch updates ensures that your assignment always has the latest security fixes.

If you enable automatic patch updates, you must still apply major updates manually.

Manually upgrading assignments in the CLI

Upgrade an assignment to use the latest storage template revision.

  1. List your Satellite storage assignments, make a note of the Satellite assignment you want to upgrade.

    ibmcloud sat storage assignment ls
    
  2. List the Satellite storage templates to see the latest available versions.

    ibmcloud sat storage template ls
    
  3. Upgrade the Satellite assignment.

    Example command to upgrade an assignment.

    ibmcloud sat storage assignment upgrade --assignment ASSIGNMENT
    

Enabling automatic patch updates for configurations and assignments in the CLI

You can use the sat storage assignment autopatch enable CLI to enable automatic patch updates for your assignments. Enabling automatic patch updates applies the latest storage template revisions (patches) automatically. You must still apply major updates manually.

  1. List your Satellite storage configurations. Make a note of the configuration ID.

    ibmcloud sat storage assignment ls
    
  2. Run one of the following example commands to enable automatic patch updates for your configuration and its associated assignments. Enter the configuration ID that you retrieved in the previous step.

    Example command to enable automatic patch updates for an assignment.

    ibmcloud sat storage assignment autopatch enable --config CONFIG  (--all | --assignment ASSIGNMENT-ID [--assignment ASSIGNMENT-ID])
    

    Example command to enable automatic patch updates for all storage assignments under a given configuration.

    ibmcloud sat storage assignment autopatch enable --config CONFIG --all
    

    Example command to disable automatic patch updates for all assignments under a specific configuration.

    ibmcloud sat storage assignment autopatch disable --config CONFIG --all
    

    Example command to disable automatic patch updates for an single assignment and a specific configuration.

    ibmcloud sat storage assignment autopatch disable --config CONFIG --assignment ASSIGNMENT-ID
    

    Example command to disable automatic patch updates for an multiple assignment and a specific configuration.

    ibmcloud sat storage assignment autopatch disable --config CONFIG --assignment ASSIGNMENT-ID --assignment ASSIGNMENT-ID
    

Upgrading a configuration and assignments in the API

You can use the /v2/storage/satellite/updateAssignment API to update your assignments with new clusters or cluster groups. Set updateConfigVersion to true to apply the revision update.

  1. Copy the following example request and replace the variables for the cluster groups and assignments that you want to update.

    curl -X PATCH "https://containers.cloud.ibm.com/global/v2/storage/satellite/updateAssignment" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d "{ \"groups\": [ \"CLUSTER-GROUPS\" ], \"name\": \"ASSIGNMENT-NAME\", \"updateConfigVersion\": true, \"uuid\": \"ASSIGNMENT-ID\"}"
    
  2. Run the request.

  3. Get the details of you assignment to verify the update.

    curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignment?uuid=ASSIGNMENT-ID" -H "accept: application/json" -H "Authorization: Bearer TOKEN"
    

Enabling automatic patch updates for assignments in the API

You can use the /v2/storage/satellite/setAssignmentAutoupgrade API to enable automatic patch updates for your assignments. Enabling automatic patch updates applies the latest storage template revisions (patches) automatically. You must still apply major updates manually.

  1. Copy the following example request and replace the variables for the cluster groups and assignments that you want to update.

    curl -X PATCH "https://containers.cloud.ibm.com/global/v2/storage/satellite/setAssignmentAutoupgrade" -H "accept: application/json" -H "Authorization: Bearer TOKEN" -H "Content-Type: application/json" -d { "config": "string", "controller": "string", "autopatch": boolean,"assignment" : { "all": boolean, "uuid": ["string", "string", ...], } }
    
  2. Run the request.

  3. Get the details of you assignment to verify the upgrade.

    curl -X GET "https://containers.cloud.ibm.com/global/v2/storage/satellite/getAssignment?uuid=ASSIGNMENT-ID" -H "accept: application/json" -H "Authorization: Bearer TOKEN"
    

Deploying an app that uses ONTAP-NAS storage

You can use the trident-kubectl-nas driver to deploy apps that use your NetApp ONTAP-NAS storage in your clusters.

  1. Create a PVC configuration file that uses one of the sat-netapp storage classes.

    apiVersion: v1
    kind: PersistentVolumeClaim
    metadata:
      name: netapp-pvc
    spec:
      accessModes:
      - ReadWriteMany
      storageClassName: sat-netapp-file-gold
      resources:
      requests:
        storage: 10Gi
    
  2. Create the PVC in your cluster.

    oc apply -f pvc.yaml
    
  3. Verify that the PVC is created. Make sure that the PVC is in a Bound status.

    oc get pvc
    

    Example output

    NAME         STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS           AGE
    netapp-pvc   Bound    pvc-acd9e5b4-0b24-4e20-ac00-69a05148c799   10Gi       RWX            sat-netapp-file-gold   39s
    
  4. Create a YAML configuration file for a pod that mounts the PVC that you created. The following example creates an nginx pod that writes the current date and time to a test.txt file on your ONTAP-NAS volume mount path.

    apiVersion: v1
    kind: Pod
    metadata:
        name: app
    spec:
        containers:
        - name: app
        image: nginx
        command: ["/bin/sh"]
        args: ["-c", "while true; do echo $(date -u) >> /test/test.txt; sleep 5; done"]
        volumeMounts:
        - name: persistent-storage
            mountPath: /test
        volumes:
        - name: persistent-storage
        persistentVolumeClaim:
            claimName: netapp-pvc
    
  5. Create the pod in your cluster.

    oc apply -f pod.yaml
    
  6. Verify that the pod is deployed. Note that it might take a few minutes for your app to get into a Running state.

    oc get pods
    

    Example output

    NAME                                READY   STATUS    RESTARTS   AGE
    app   1/1     Running   0          50s
    
  7. Verify that the app can write to your ONTAP-NAS instance.

    1. Log in to your pod.

      oc exec app -it bash
      
    2. Display the contents of the test.txt file to confirm that your app can write data to your persistent storage.

      cat /test/test.txt
      

      Example output

      Wed May 19 13:28:31 UTC 2021
      Wed May 19 13:28:37 UTC 2021
      Wed May 19 13:28:42 UTC 2021
      Wed May 19 13:28:47 UTC 2021
      
    3. Exit the pod.

      exit
      

Removing NetApp ONTAP-NAS storage from your apps

Before you remove your storage configuration, remove the app pods and PVCs that are using your NetApp storage.

  1. List your PVCs and note the name of the PVC and the corresponding PV that you want to remove.

    oc get pvc
    
  2. List all the pods that currently mount the PVC that you want to delete. If no pods are returned, you do not have any pods that currently use your PVC.

    oc get pods --all-namespaces -o=jsonpath='{range .items[*]}{"\n"}{.metadata.name}{":\t"}{range .spec.volumes[*]}{.persistentVolumeClaim.claimName}{" "}{end}{end}' | grep "<pvc_name>"
    

    Example output

    app    sat-netapp-file-gold
    
  3. If the pod is part of a deployment, delete the deployment.

    oc delete deployment <deployment_name>
    
  4. Verify that the pod or the deployment is removed.

    oc get pods
    
    oc get deployments
    
  5. Delete the PVC.

    oc delete pvc <pvc_name>
    
  6. Delete the corresponding PV.

    oc delete pv <pv_name>
    
  7. [Remove your NetApp ONTAP-NAS storage configuration from your cluster]/docs/satellite?topic=satellite-storage-netapp-ontap-nas&interface=cli#netapp-nas-template-rm-cli-2104)

Removing the NetApp ONTAP-NAS storage assignment and configuration from the CLI

Use the CLI to remove a storage assignment and storage configuration.

  1. List your storage assignments and find the one that you used for your cluster.

    ibmcloud sat storage assignment ls (--cluster CLUSTER | --config CONFIG | --location LOCATION | --service-cluster-id CLUSTER)
    
  2. Remove the assignment. After the assignment is removed, the NetApp ONTAP-NAS driver pods and storage class are removed from all clusters that were part of the storage assignment.

    ibmcloud sat storage assignment rm --assignment <assignment_ID>
    
  3. Verify that the NetApp ONTAP-NAS driver is removed from your cluster. List the storage classes in your cluster and verify that the NetApp ONTAP-NAS storage class is removed.

    oc get sc
    
  4. List the pods in the trident namespace and verify that the NetApp ONTAP-NAS storage driver pods are removed.

    oc get pods -n trident
    
  5. Optional: List your storage configurations and remove your NetApp configuration.

    ibmcloud sat storage config ls
    
    ibmcloud sat storage config rm --config <config_name>
    
  6. Next steps: Remove the NetApp Trident operator from your cluster.

Removing the NetApp ONTAP-NAS storage assignment and configuration from the console

Use the console to remove a storage assignment and storage configuration.

  1. From the Satellite storage dashboard, select the storage configuration you want to delete.
  2. Select Actions > Delete
  3. Enter the name of your storage configuration.
  4. Select Delete.

Parameter reference

22.04 parameter reference

Table 1. 22.04 parameter reference
Display name CLI option Type Description Required? Default value
Management LIF managementLIF Config The IP address of the Management LIF. true N/A
Data LIF dataLIF Config The IP address of the Data LIF. true N/A
SVM svm Config The name of the SVM. true N/A
User Name username Secret The username to connect to the storage device. true N/A
User Password password Secret The password to connect to the storage device. true N/A
Export Policy exportPolicy Config The NAS option for the NFS export policy. true default
Limit Volume Size limitVolumeSize Config Maximum requestable volume size (in Gibibytes) and qtree parent volume size true 50Gi
Limit AggregateUsage limitAggregateUsage Config Fail provisioning if usage is greater than this percentage. true 80%
NFS Mount Options nfsMountOptions Config The NFS mount options. true nfsvers=4

22.10 parameter reference

Table 2. 22.10 parameter reference
Display name CLI option Type Description Required? Default value
Management LIF managementLIF Config The IP address of the Management LIF. true N/A
Data LIF dataLIF Config The IP address of the Data LIF. true N/A
SVM svm Config The name of the SVM. true N/A
User Name username Secret The username to connect to the storage device. true N/A
User Password password Secret The password to connect to the storage device. true N/A
Export Policy exportPolicy Config The NAS option for the NFS export policy. true default
Limit Volume Size limitVolumeSize Config Maximum requestable volume size (in Gibibytes) and qtree parent volume size true 50Gi
Limit AggregateUsage limitAggregateUsage Config Fail provisioning if usage is greater than this percentage. true 80%
NFS Mount Options nfsMountOptions Config The NFS mount options. true nfsvers=4

24.02 parameter reference

Table 3. 24.02 parameter reference
Display name CLI option Type Description Required? Default value
Management LIF managementLIF Config The IP address of the Management LIF. true N/A
Data LIF dataLIF Config The IP address of the Data LIF. true N/A
SVM svm Config The name of the SVM. true N/A
User Name username Secret The username to connect to the storage device. true N/A
User Password password Secret The password to connect to the storage device. true N/A
Export Policy exportPolicy Config The NAS option for the NFS export policy. true default
Limit Volume Size limitVolumeSize Config Maximum requestable volume size (in Gibibytes) and qtree parent volume size true 50Gi
Limit AggregateUsage limitAggregateUsage Config Fail provisioning if usage is greater than this percentage. true 80%
NFS Mount Options nfsMountOptions Config The NFS mount options. true nfsvers=4

Storage class reference for NetApp ONTAP-NAS

Before you deploy an app that uses the sat-netapp storage classes, review the following notes.

  • By default, the sat-netapp-file-gold storage class doesn't include any QoS limits (unlimited IOPS).
  • To use the sat-netapp-file-silver and sat-netapp-file-bronze storage classes, you must create corresponding silver and bronze QoS policy groups on the storage controller and define the QoS limits. To create a policy group on the storage system, log in to the system CLI and run the **netapp1::> qos policy-group create -policy-group <policy_group_name> -vserver <svm_name> [-min-throughput <min_IOPS>] -max-throughput <max_IOPS>** command.
  • The min-throughput option is supported only on all-flash systems. For more information about creating and managing QoS Policy groups, see the ONTAP 9 Storage Management documentation.
  • To use an encrypted storage class, NetApp Volume Encryption (NVE) must be enabled on your storage system by using either the NetApp ONTAP onboard key manager or a supported (off-box) third-party key manager, such as IBM 's TKLM key manager. To enable the onboard key manager, run the netapp1::> security key-manager onboard enable command. For more information about configuring encryption, see the ONTAP 9 Security and Data Encryption documentation.

Review the Satellite storage classes for NetApp ONTAP-NAS. You can describe storage classes in the command line with the oc describe sc <storage-class-name> command.

NetApp ONTAP-NAS storage class reference.
Storage class name Type File system IOPs Encryption Reclaim policy
sat-netapp-file-gold Default ONTAP-NAS NFS no QoS limits Encryption disabled. Delete
sat-netapp-file-gold-encrypted ONTAP-NAS NFS no QoS limits Encryption enabled. Delete
sat-netapp-file-silver ONTAP-NAS NFS User defined QoS limit. Encryption disabled. Delete
sat-netapp-file-silver-encrypted ONTAP-NAS NFS User defined QoS limit. Encryption enabled. Delete
sat-netapp-file-bronze ONTAP-NAS NFS User-defined QoS limit. Encryption disabled. Delete
sat-netapp-file-bronze-encrypted ONTAP-NAS NFS User-defined QoS limit. Encryption enabled. Delete

Getting help and support for NetApp ONTAP-NAS

If you run into an issue with NetApp Trident, you can visit the NetApp support page.