Go to the docs for the latest release.
Using ONTAP as persistent storage for Kubernetes
Cloud Manager can automate the deployment of NetApp Trident on Kubernetes clusters so you can use ONTAP as persistent storage for containers. This works with Cloud Volumes ONTAP and on-prem ONTAP clusters.
If you deploy Kubernetes clusters using the NetApp Kubernetes Service, Cloud Manager can automatically discover the clusters from your NetApp Cloud Central account. If that’s the case, skip the first two steps and start with step 3.
Verify network connectivity
A network connection must be available between Cloud Manager and the Kubernetes clusters, and from the Kubernetes clusters to ONTAP systems.
Cloud Manager needs an outbound internet connection to access the following endpoints when installing Trident:
Cloud Manager installs Trident on a Kubernetes cluster when you connect a working environment to the cluster.
Upload Kubernetes configuration files to Cloud Manager
For each Kubernetes cluster, the Account Admin needs to upload a configuration file (kubeconfig) that is in YAML format. After you upload the file, Cloud Manager verifies connectivity to the cluster and saves an encrypted copy of the kubeconfig file.
Click Kubernetes Clusters > Discover > Upload File and select the kubeconfig file.
Connect your working environments to Kubernetes clusters
From the working environment, click the Kubernetes icon and follow the prompts. You can connect different clusters to different ONTAP systems and multiple clusters to the same ONTAP system.
You have the option to set the NetApp storage class as the default storage class for the Kubernetes cluster. When a user creates a persistent volume, the Kubernetes cluster can use connected ONTAP systems as the backend storage by default.
Start provisioning Persistent Volumes
Request and manage Persistent Volumes using native Kubernetes interfaces and constructs. Cloud Manager creates four Kubernetes storage classes that you can use when provisioning Persistent Volumes:
netapp-file: for binding Persistent Volumes to single-node ONTAP systems
netapp-file-san: for binding iSCSI Persistent Volumes to single-node ONTAP systems
netapp-file-redundant: for binding Persistent Volumes to ONTAP HA pairs
netapp-file-redundant-san: for binding iSCSI Persistent Volumes to ONTAP HA pairs
Cloud Manager configures Trident to use the following provisioning options by default:
The default Snapshot policy
Accessible Snapshot directory