Skip to main content

Upgrade Trident protect

Contributors netapp-shwetav netapp-mwallis netapp-aruldeepa
PDFs

You can upgrade Trident protect to the latest version to take advantage of new features or bug fixes.

Note

  • When you upgrade from version 24.10, snapshots running during the upgrade might fail. This failure does not prevent future snapshots, whether manual or scheduled, from being created. If a snapshot fails during the upgrade, you can manually create a new snapshot to ensure your application is protected.

    To avoid potential failures, you can disable all snapshot schedules before the upgrade and re-enable them afterward. However, this results in missing any scheduled snapshots during the upgrade period.

  • For private registry installations, ensure the required Helm chart and images for the target version are available in your private registry, and verify your custom Helm values are compatible with the new chart version. For more information, refer to Install Trident protect from a private registry.

To upgrade Trident protect, perform the following steps.

Steps

  1. Update the Trident Helm repository:

    helm repo update

  2. Upgrade the Trident protect CRDs:

    Note This step is required if you are upgrading from a version earlier than 25.06, as the CRDs are now included in the Trident protect Helm chart.

    1. Run this command to shift management of CRDs from trident-protect-crds to trident-protect:

      kubectl get crd | grep protect.trident.netapp.io | awk '{print $1}' | xargs -I {} kubectl patch crd {} --type merge -p '{"metadata":{"annotations":{"meta.helm.sh/release-name": "trident-protect"}}}'

    2. Run this command to delete the Helm secret for the trident-protect-crds chart:

      Note Do not uninstall the trident-protect-crds chart using Helm, as this could remove your CRDs and any related data. 
      kubectl delete secret -n trident-protect -l name=trident-protect-crds,owner=helm

  3. Upgrade Trident protect:

    helm upgrade trident-protect netapp-trident-protect/trident-protect --version 100.2510.0 --namespace trident-protect
    Note You can configure the logging level during upgrade by adding --set logLevel=debug to the upgrade command. The default logging level is warn. Debug logging is recommended for troubleshooting as it helps NetApp support diagnose issues without requiring log level changes or problem reproduction.