Skip to main content
A newer release of this product is available.

Requirements

Contributors juliantap
PDFs

Before installing Astra Trident you should review these general system requirements. Specific backends might have additional requirements.

Critical information about Astra Trident 23.01

You must read the following critical information about Astra Trident.

Critical information about Astra Trident

  • Kubernetes 1.27 is now supported in Trident. Upgrade Trident prior to upgrading Kubernetes.

  • Astra Trident strictly enforces the use of multipathing configuration in SAN environments, with a recommended value of find_multipaths: no in multipath.conf file.

    Use of non-multipathing configuration or use of find_multipaths: yes or find_multipaths: smart value in multipath.conf file will result in mount failures. Trident has recommended the use of find_multipaths: no since the 21.07 release.

Supported frontends (orchestrators)

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

  • Anthos On-Prem (VMware) and Anthos on bare metal 1.12

  • Kubernetes 1.21 - 1.27

  • Mirantis Kubernetes Engine 3.5

  • OpenShift 4.9 - 4.12

The Trident operator is supported with these releases:

  • Anthos On-Prem (VMware) and Anthos on bare metal 1.12

  • Kubernetes 1.21 - 1.27

  • OpenShift 4.9 - 4.12

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.

Warning Before upgrading a Kubernetes cluster from 1.24 to 1.25 or later that has Astra Trident installed, see Upgrade a Helm-based operator installation.

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

  • Cloud Volumes ONTAP

  • Cloud Volumes Service for GCP

  • FAS/AFF/Select 9.5 or later

  • NetApp All SAN Array (ASA)

  • NetApp HCI/Element software 11 or above

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.21 - 1.27

No

Volume Snapshots

1.21 - 1.27

No

PVC from Volume Snapshots

1.21 - 1.27

No

iSCSI PV resize

1.21 - 1.27

No

ONTAP Bidirectional CHAP

1.21 - 1.27

No

Dynamic Export Policies

1.21 - 1.27

No

Trident Operator

1.21 - 1.27

No

CSI Topology

1.21 - 1.27

No

Tested host operating systems

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

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

  • RHEL 8+ (AMD64 and ARM64)

  • Ubuntu 22.04 or later (AMD64 and ARM64)

  • Windows Server 2019 (AMD64)

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.

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

Host configuration

All worker nodes in the Kubernetes cluster must be able to mount the volumes you have provisioned for your pods. To prepare the worker nodes, you must install NFS or iSCSI tools based on your driver selection.

Prepare the worker node

Storage system configuration

Astra Trident might require changes to a storage system before a backend configuration can use it.

Configure backends

Astra Trident ports

Astra Trident requires access to specific ports for communication.

Astra Trident ports

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.21.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.22.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.23.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.24.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.25.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.26.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)

v1.27.0

  • docker.io/netapp/trident:23.04.0

  • docker.io/netapp/trident-autosupport:23.04

  • registry.k8s.io/sig-storage/csi-provisioner:v3.4.1

  • registry.k8s.io/sig-storage/csi-attacher:v4.2.0

  • registry.k8s.io/sig-storage/csi-resizer:v1.7.0

  • registry.k8s.io/sig-storage/csi-snapshotter:v6.2.1

  • registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.7.0

  • docker.io/netapp/trident-operator:23.04.0 (optional)
Note On Kubernetes version 1.21 and above, use the validated registry.k8s.gcr.io/sig-storage/csi-snapshotter:v6.x image only if the v1 version is serving the volumesnapshots.snapshot.storage.k8s.gcr.io CRD. If the v1beta1 version is serving the CRD with/without the v1 version, use the validated registry.k8s.gcr.io/sig-storage/csi-snapshotter:v3.x image.