Backend configuration

A Trident 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.

Trident will automatically offer up storage pools from backends that together match the requirements defined by a storage class.

To get started, choose the storage system type that you will be using as a backend:

• Azure NetApp Files
  • Preparation
  • Backend configuration options
  • Example configurations
• Cloud Volumes Service for AWS
  • Preparation
  • Backend configuration options
  • Example configurations
• Cloud Volumes Service for GCP
  • Preparation
  • Backend configuration options
  • Example configurations
• Element (HCI/SolidFire)
  • Preparation
  • Backend configuration options
  • Example configuration
  • Using access groups
• ONTAP (AFF/FAS/Select/Cloud)
  • Choosing a driver
  • Preparation
    • ontap-nas, ontap-nas-economy, ontap-nas-flexgroups
      • Dynamic Export Policies with ONTAP NAS
        • Prerequisites
        • How it works
        • Updating your Kubernetes cluster configuration
        • Updating legacy backends
    • ontap-san, ontap-san-economy
      • Using CHAP with ONTAP SAN drivers
        • Configuration
        • How it works
        • Rotating credentials and updating backends
  • Backend configuration options
  • Example configurations
  • User permissions
• SANtricity (E-Series)
  • Preparation
  • Backend configuration options
  • Example configuration