The Upgrade Guide details the procedure for upgrading to the latest version of Trident.
Trident 20.01 provides a set of Prometheus metrics that can be used to obtain
insight on how Trident operates. You can now define a Prometheus target to gather
the metrics exposed by Trident and obtain information on the backends it manages,
the volumes it creates and so on. Trident’s metrics are exposed on the target port
8001. These metrics are enabled by default when Trident is installed; to disable
them from being reported, you will have to generate custom YAMLs (using the
--generate-custom-yaml flag) and edit them to remove the
from being invoked for the
This blog is a great place to start. It explains how Prometheus and Grafana can be used with Trident 20.01 and above to retrieve metrics. The blog explains how you can run Prometheus as an operator in your Kubernetes cluster and the creation of a ServiceMonitor to obtain Trident’s metrics.
The uninstall command in tridentctl will remove all of the resources associated with Trident except for the CRDs and related objects, making it easy to run the installer again to update to a more recent version.
./tridentctl uninstall -n <namespace>
To perform a complete removal of Trident, you will need to remove the finalizers for the CRDs created by Trident and delete the CRDs. Refer the Troubleshooting Guide for the steps to completely uninstall Trident.
Downgrading to a previous release of Trident is not recommended and should
not be performed unless absolutely neccessary. Downgrades to versions
and earlier are not supported.
Refer the downgrade section for considerations and
factors that can influence your decision to downgrade.