Supported frontends (orchestrators)¶
Trident supports multiple container engines and orchestrators, including:
- Docker 17.06 (CE or EE) or later (latest: 18.09)
- Docker Enterprise Edition 17.06 or later (latest: 2.1)
- Kubernetes 1.10 or later (latest: 1.14)
- OpenShift 3.8 or later (latest: 3.11)
In addition, Trident should work with any distribution of Docker or Kubernetes that uses one of the supported versions as a base, such as Rancher or Tectonic.
Supported backends (storage)¶
To use Trident, you need one or more of the following supported backends:
- FAS/AFF/Select/Cloud ONTAP 8.3 or later
- SolidFire Element OS 8 or later
- E/EF-Series SANtricity
- Cloud Volumes Service for AWS
Supported host operating systems¶
By default Trident itself runs in a container, therefore it will run on any Linux worker.
However, those workers do need to be able to mount the volumes that Trident provides using the standard NFS client or iSCSI initiator, depending on the backend(s) you’re using.
These are the Linux distributions that are known to work:
- Debian 8 or later
- Ubuntu 16.04 or later
- CentOS 7.0 or later
- RHEL 7.0 or later
- CoreOS 1353.8.0 or later
tridentctl utility also runs on any of these distributions of Linux.
Depending on the backend(s) in use, NFS and/or iSCSI utilities must be installed on all of the workers in the cluster. See the worker preparation guide for details.
Storage system configuration¶
Trident may require some changes to a storage system before a backend configuration can use it. See the backend configuration guide for details.
External etcd cluster (Optional)¶
Trident uses etcd v3.1.3 or later to store its metadata. The standard installation process includes an etcd container that is managed by Trident and backed by a volume from a supported storage system, so there is no need to install it separately.
If you would prefer to use a separate external etcd cluster instead, Trident can easily be configured to do so. See the external etcd guide for details.