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:

If you have questions about Trident, please reach out using the comments below, on Slack, or on the GitHub issue tracker for Trident.

Andrew Sullivan on GithubAndrew Sullivan on Twitter
Andrew Sullivan
Technical Marketing Engineer at NetApp
Andrew has worked in the information technology industry for over 10 years, with a rich history of database development, DevOps experience, and virtualization. He is currently focused on storage and virtualization automation, and driving simplicity into everyday workflows.

Pin It on Pinterest