Managing Trident¶
Installing Trident¶
Follow the extensive deployment guide.
Updating Trident¶
The plugin is not in the data path, therefore you can safely upgrade it without any impact to volumes that are in use. As with any plugin, during the upgrade process there will be a brief period where ‘docker volume’ commands directed at the plugin will not succeed, and applications will be unable to mount volumes until the plugin is running again. Under most circumstances, this is a matter of seconds.
List the existing volumes:
docker volume ls DRIVER VOLUME NAME netapp:latest my_volume
Disable the plugin:
docker plugin disable -f netapp:latest docker plugin ls ID NAME DESCRIPTION ENABLED 7067f39a5df5 netapp:latest nDVP - NetApp Docker Volume Plugin false
Upgrade the plugin:
docker plugin upgrade --skip-remote-check --grant-all-permissions netapp:latest netapp/trident-plugin:19.10
Note
The 18.01 release of Trident replaces the nDVP. You should upgrade directly from the netapp/ndvp-plugin image to the netapp/trident-plugin image.
Enable the plugin:
docker plugin enable netapp:latest
Verify that the plugin is enabled:
docker plugin ls ID NAME DESCRIPTION ENABLED 7067f39a5df5 netapp:latest Trident - NetApp Docker Volume Plugin true
Verify that the volumes are visible:
docker volume ls DRIVER VOLUME NAME netapp:latest my_volume
Uninstalling Trident¶
Note
Do not uninstall the plugin in order to upgrade it, as Docker may become confused as to which plugin owns any existing volumes; use the upgrade instructions in the previous section instead.
Remove any volumes that the plugin created.
Disable the plugin:
docker plugin disable netapp:latest docker plugin ls ID NAME DESCRIPTION ENABLED 7067f39a5df5 netapp:latest nDVP - NetApp Docker Volume Plugin false
Remove the plugin:
docker plugin rm netapp:latest