Recently NetApp released an open source project known as Trident, the first external storage provisioner for Kubernetes leveraging on-premises storage. Prior to release 1.4, Kubernetes had the ability to dynamically assign storage to applications using its persistent volume framework, however, this required pre-provisioning of storage resources introduced to Kubernetes by an administrator.
Trident enables the use of the new storage class concept in Kubernetes, acting as a provisioning controller that watches for persistent volume requests and creates them on-demand. This means that when a pod requests storage from a storage class that Trident is responsible for, it will provision a volume that meets those requirements and make it available to the pod in real-time.
This post is the first in a series which introduces Trident, its functionality, and how it relates to Kubernetes’ intrinsic storage management framework. The remainder of the series will focus on the installation, configuration, and use of Trident.
We know you’re anxious to get started, so the entire video series is already available if you want to jump ahead:
- Installing and configuring Trident
- Using Trident to provision basic persistent volumes for Kubernetes
- Advanced Kubernetes persistent volume provisioning with Trident
- Using the Trident REST API to manage storage for any application