Table of Contents
Updating and Upgrading Tungsten Dashboard is a simple process and handled by the same install.pl command that was used for the initial installation.
When executing install.pl, the command will automatically determine whether you are updating an existing installation with new configuration variables or upgrading to a new Tungsten Dashboard release.
Known issue
Updating your running environment from no TLS (http) to TLS (https) using docker-compose installation method is currently unavailable. Please use upgrade instead - download an unmodified tungsten-dashboard release archive, extract it, and follow the install.pl script instructions.
The install.pl command will update an existing configuration if it is executed from within the same directory that was previously used for the initial installation.
The update will detect modifications to the various configuration variables and during the process you will be prompted for the same configuration options as when the installation was performed.
It is recommended to backup your modified config files (docker-compose.yml and
.env file for docker-compose method and values.yaml file for kubernetes).
This process could be thought of as the Tungsten Clustering equivalent of tpm update
The install.pl command will upgrade an existing configuration if it is executed from within the new directory which was created by unpacking the software archive..
The upgrade will prompt for the same configuration options as when the initial installation was performed, and detect an existing Tungsten Dashboard version running. You will then be prompted to continue. An example of the process detecting the running dashboard is as follows:
Example of a detected docker-compose deployment:
Docker service 'tungsten-dashboard' is already running. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 52594391c843 tungsten-dashboard:8.0.0 "java -jar /app/dash…" 40 minutes ago Up 40 minutes (healthy) tungsten-dashboard-service-1 Do you want to upgrade the existing deployment? [y/N]:
Example of a detected kubernetes deployment:
Kubernetes deployment 'tungsten-dashboard' already exists. NAME READY UP-TO-DATE AVAILABLE AGE tungsten-dashboard 1/1 1 1 40m14s Do you want to upgrade the existing deployment? [y/N]:
This process could be thought of as the Tungsten Clustering equivalent of tools/tpm update --replace-release