Quick start for Trident
You can install Trident and start managing storage resources in a few steps. Before getting started, review Trident requirements.
|
For Docker, refer to Trident for Docker. |
![One](https://raw.githubusercontent.com/NetAppDocs/common/main/media/number-1.png)
All worker nodes in the Kubernetes cluster must be able to mount the volumes you have provisioned for your pods.
![Two](https://raw.githubusercontent.com/NetAppDocs/common/main/media/number-2.png)
Trident offers several installation methods and modes optimized for a variety of environments and organizations.
![Three](https://raw.githubusercontent.com/NetAppDocs/common/main/media/number-3.png)
A backend defines the relationship between Trident and a storage system. It tells Trident how to communicate with that storage system and how Trident should provision volumes from it.
Configure a backend for your storage system
![Four](https://raw.githubusercontent.com/NetAppDocs/common/main/media/number-4.png)
The Kubernetes StorageClass object specifies Trident as the provisioner and allows you to create a storage class to provision volumes with customizable attributes. Trident creates a matching storage class for Kubernetes objects that specify the Trident provisioner.
![Five](https://raw.githubusercontent.com/NetAppDocs/common/main/media/number-5.png)
A PersistentVolume (PV) is a physical storage resource provisioned by the cluster administrator on a Kubernetes cluster. The PersistentVolumeClaim (PVC) is a request for access to the PersistentVolume on the cluster.
Create a PersistentVolume (PV) and a PersistentVolumeClaim (PVC) that uses the configured Kubernetes StorageClass to request access to the PV. You can then mount the PV to a pod.
What's next?
You can now add additional backends, manage storage classes, manage backends, and perform volume operations.