Requirements
Suggest changes
PDFs
Get started by reviewing the supported frontends, backends, and host configuration.
|
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.8, 1.9, 1.10
-
Kubernetes 1.17 or later (latest: 1.23)
-
Mirantis Kubernetes Engine 3.4
-
OpenShift 4.7, 4.8, 4.9
The Trident operator is supported with these releases:
-
Anthos On-Prem (VMware) and Anthos on bare metal 1.8, 1.9, 1.10
-
Kubernetes 1.17 or later (latest: 1.23)
-
OpenShift 4.7, 4.8, 4.9
|
|
Red Hat OpenShift Container Platform users might observe their initiatorname.iscsi file to be blank if using any version below 4.6.8. This is a bug that has been identified by RedHat to be fixed with OpenShift 4.6.8. See this bug fix announcement. NetApp recommends that you use Astra Trident on OpenShift 4.6.8 and later. |
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.17 and later |
No |
Volume Snapshots |
1.17 and later |
No |
PVC from Volume Snapshots |
1.17 and later |
No |
iSCSI PV resize |
1.17 and later |
No |
ONTAP Bidirectional CHAP |
1.17 and later |
No |
Dynamic Export Policies |
1.17 and later |
No |
Trident Operator |
1.17 and later |
No |
Auto Worker Node Prep (beta) |
1.17 and later |
No |
CSI Topology |
1.17 and later |
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.17.0 |
|
v1.18.0 |
|
v1.19.0 |
|
v1.20.0 |
|
v1.21.0 |
|
v1.22.0 |
|
v1.23.0 |
|
|
|
On Kubernetes version 1.20 and later, use the validated k8s.gcr.io/sig-storage/csi-snapshotter:v4.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.
|