7. Deploying Trident¶
The guidelines in this section provide recommendations for Trident installation with various Kubernetes configurations and considerations. As with all the other recommendations in this guide, each of these suggestions should be carefully considered to determine if it’s appropriate and will provide benefit to your deployment.
7.1. Supported Kubernetes cluster architectures¶
Trident is supported with the following Kubernetes architectures. In each of the Kubernetes architectures below, the installation steps remain relatively the same except for the ones which have an asterick.
Kubernetes Cluster Architectures Supported Normal Installation Single master, compute Yes Yes Multiple master, compute Yes Yes Master, etcd, compute Yes* No Master, infrastructure, compute Yes Yes
The cell marked with an asterik above has an external production etcd cluster and requires different installation steps for deploying Trident. The Trident etcd documentation discusses in detail how to freshly deploy Trident on an external etcd cluster. It also mentions how to migrate existing Trident deployment to an external etcd cluster as well.
7.2. Trident installation modes¶
Three ways to install Trident are discussed in this chapter.
Normal install mode
Normal installation involves running the
tridentctl install -n trident command which deploys the Trident pod on the Kubernetes cluster. Trident installation is quite a straightforward process. For more information on installation and provisioning of volumes, refer to the Deploying documentation.
Offline install mode
In many organizations, production and development environments do not have access to public repositories for pulling and posting images as these environments are completely secured and restricted. Such environments only allow pulling images from trusted private repositories.
In such scenarios, make sure that a private registry instance is available. Then trident and etcd images should be downloaded from a bastion host with internet access and pushed on to the private registry. To install Trident in offline mode, just issue the
tridentctl install -n trident command with the
--etcd-image and the
--trident-image parameter with the appropriate image name and location. For more information on how to install Trident in offline mode, please examine the blog on Installing Trident for Kubernetes from a Private Registry.
Remote install mode
Trident can be installed on a Kubernetes cluster from a remote machine. To do a remote install, install the appropriate version of
kubectl on the remote machine from where you would be running the
tridentctl install command. Copy the configuration files from the Kubernetes cluster and set the KUBECONFIG environment variable on the remote machine. Initiate a
kubectl get nodes command to verify you can connect to the required Kubernetes cluster. Complete the Trident deployment from the remote machine using the normal installation steps.
7.3. Trident CSI installation¶
NetApp does not support running Trident in CSI mode in production. It is reserved for development purposes at this time. You’re welcome to try it, and we would love to hear any feedback you may have if you do! More information regarding CSI can be found in the Trident documentation.
7.4. Trident Installation on Docker UCP 3.1¶
Docker EE Universal Control Plane (UCP) is the cluster management layer that sits on top of the Docker Enterprise Engine. Once deployed, administrators interact with their cluster via UCP instead of each node’s individual Docker engines. Since the UCP supports both Kubernetes and Docker via a Web UI or CLI, administrators can use either a Kubernetes YAMLs or Docker Compose files to deploy images from the centralized location. It also provides cluster-wide monitoring of deployed containers, services, and pods.
Installing Trident for Kubernetes on UCP managed nodes is similar to installing Trident on Kubernetes. Refer to the following documentation for instructions on how to install Trident for Kubernetes.
Please note that starting with Docker EE 2.1 UCP and Trident 19.01, it’s no longer required to specify the
--ucp-bearer-token parameters while installing and uninstalling Trident. Deploy the
tridentctl install -n <namespace> command to start the installation on the UCP managed nodes.
7.5. Trident Installation on NetApp Kubernetes Service¶
NetApp Kubernetes Service (NKS) is a universal control plane through which production grade Kubernetes clusters can be provisioned and run on the cloud provider of choice. NKS can quickly build a cluster on the cloud of your choice and easily manage your Kubernetes cluster from a single pane of glass.
Installing Trident for Kubernetes on NKS is similar to installing Trident on Kubernetes when used with Cloud Volumes ONTAP. Refer to the following documentation for instructions on how to install Trident for Kubernetes.
Using Trident we can set Cloud Volumes ONTAP (CVO) and Cloud Volumes Services (CVS) with AWS as a storage backend for NKS. CVO and CVS are storage services that can be spun up on different cloud providers giving flexibility for users to maintain their Kubernetes persistent data in their respective cloud. To use Cloud Volume ONTAP as persistent storage for the Kubernetes cluster provisioned through NKS, upload the configuration file (kubeconfig) in YAML format on the OnCommand Cloud Manager (OCCM). Cloud Manager can automate the deployment of NetApp Trident on Kubernetes clusters so you can use Cloud Volumes ONTAP as persistent storage for containers.
You can connect different clusters to different Cloud Volumes ONTAP systems and multiple clusters to the same Cloud Volumes ONTAP system.
7.6. Recommendations for all deployments¶
7.6.1. Deploy Trident to a dedicated namespace¶
Namespaces provide administrative separation between different applications and are a barrier for resource sharing, for example, a PVC from one namespace cannot be consumed from another. Trident provides PV resources to all namespaces in the Kubernetes cluster and consequently leverages a service account which has elevated privileges.
Additionally, access to the Trident pod may enable a user to access storage system credentials and other sensitive information. It is important to ensure that application users and management applications do not have the ability to access the Trident object definitions or the pods themselves.
7.6.2. Use quotas and range limits to control storage consumption¶
Kubernetes has two features which, when combined, provide a powerful mechanism for limiting the resource consumption by applications. The storage quota mechanism allows the administrator to implement global, and storage class specific, capacity and object count consumption limits on a per-namespace basis. Further, using a range limit will ensure that the PVC requests must be within both a minimum and maximum value before the request is forwarded to the provisioner.
These values are defined on a per-namespace basis, which means that each namespace will need to have values defined which fall in line with their resource requirements. An example of how to leverage quotas can be found on netapp.io.
7.7. Deploying Trident to OpenShift¶
OpenShift uses Kubernetes for the underlying container orchestrator. Consequently, the same recommendations will apply when using Trident with Kubernetes or OpenShift. However, there are some minor additions when using OpenShift which should be taken into consideration.
7.7.1. Deploy Trident to infrastructure nodes¶
Trident is a core service to the OpenShift cluster, provisioning and managing the volumes used across all projects. Consideration should be given to deploying Trident to the infrastructure nodes in order to provide the same level of care and concern.
To deploy Trident to the infrastructure nodes, the project for Trident must be created by an administrator using the oc adm command. This prevents the project from inheriting the default node selector, which forces the pod to execute on compute nodes.
# create the project which Trident will be deployed to using # the non-default node selector oc adm new-project <project_name> --node-selector="region=infra" # deploy Trident using the project name tridentctl install -n <project_name>
The result of the above command is that any pod deployed to the project will be scheduled to nodes which have the tag “
region=infra”. This also removes the default node selector used by other projects which schedule pods to nodes which have the label “