Requirements

Contributors juliantap gnarl

Get started by reviewing the supported frontends, backends, and host configuration.

Note To learn about the ports that Astra Trident uses, see here.

Supported frontends (orchestrators)

Astra Trident supports multiple container engines and orchestrators, including the following:

  • Anthos On-Prem (VMware) and Anthos on bare metal 1.9, 1.10, 1.11

  • Kubernetes 1.18 - 1.24

  • Mirantis Kubernetes Engine 3.4

  • OpenShift 4.7, 4.8, 4.9, 4.10

The Trident operator is supported with these releases:

  • Anthos On-Prem (VMware) and Anthos on bare metal 1.9, 1.10, 1.11

  • Kubernetes 1.18 - 1.24

  • OpenShift 4.7, 4.8, 4.9, 4.10

Astra Trident also works with a host of other fully-managed and self-managed Kubernetes offerings, including Google Kubernetes Engine (GKE), Amazon Elastic Kubernetes Services (EKS), Azure Kubernetes Service (AKS), Rancher, and VMWare Tanzu Portfolio.

Supported backends (storage)

To use Astra Trident, you need one or more of the following supported backends:

  • Amazon FSx for NetApp ONTAP

  • Azure NetApp Files

  • Astra Data Store

  • Cloud Volumes ONTAP

  • Cloud Volumes Service for GCP

  • FAS/AFF/Select 9.3 or later

  • NetApp All SAN Array (ASA)

  • NetApp HCI/Element software 11 or later

Feature requirements

The table below summarizes the features available with this release of
Astra Trident and the versions of Kubernetes it supports.

Feature Kubernetes version Feature gates required?

CSI Trident

1.18 - 1.24

No

Volume Snapshots

1.18 - 1.24

No

PVC from Volume Snapshots

1.18 - 1.24

No

iSCSI PV resize

1.18 - 1.24

No

ONTAP Bidirectional CHAP

1.18 - 1.24

No

Dynamic Export Policies

1.18 - 1.24

No

Trident Operator

1.18 - 1.24

No

Auto Worker Node Prep (beta)

1.18 - 1.24

No

CSI Topology

1.18 - 1.24

No

Tested host operating systems

By default, Astra Trident runs in a container and will, therefore, run on any Linux worker. However, those workers need to be able to mount the volumes that Astra Trident provides using the standard NFS client or iSCSI initiator, depending on the backends you are using.

Though Astra Trident does not officially "support" specific operating systems, the following Linux distributions are known to work:

  • RedHat CoreOS (RHCOS) versions as supported by OpenShift Container Platform

  • RHEL or CentOS 7.4 or later

  • Ubuntu 18.04 or later

The tridentctl utility also runs on any of these distributions of Linux.

Host configuration

Depending on the backend(s) in use, NFS and/or iSCSI utilities should be installed on all of the workers in the cluster. See here for more information.

Storage system configuration

Astra Trident might require some changes to a storage system before a backend configuration can use it. See here for details.

Container images and corresponding Kubernetes versions

For air-gapped installations, the following list is a reference of container images needed to install Astra Trident. Use the tridentctl images command to verify the list of needed container images.

Kubernetes version Container image

v1.18.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

v1.19.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

v1.20.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

v1.21.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

v1.22.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

v1.23.0

  • netapp/trident:22.04.0

  • netapp/trident-autosupport:22.04

  • k8s.gcr.io/sig-storage/csi-provisioner:v2.2.2

  • k8s.gcr.io/sig-storage/csi-attacher:v3.4.0

  • k8s.gcr.io/sig-storage/csi-resizer:v1.4.0

  • k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3

  • k8s.gcr.io/sig-storage/csi-node-driver-registrar:v2.5.0

  • netapp/trident-operator:22.04.0 (optional)

Note On Kubernetes version 1.20 and above, use the validated k8s.gcr.io/sig-storage/csi-snapshotter:v5.x image only if the v1 version is serving the volumesnapshots.snapshot.storage.k8s.io CRD. If the v1beta1 version is serving the CRD with/without the v1 version, use the validated k8s.gcr.io/sig-storage/csi-snapshotter:v3.x image.