Upgrading an application¶
- Release a new version of the application by pushing an image with the new version tag to Docker Hub (or whatever Docker repository is used).
- Update the chart in the charts repository to install the current version.
For charts using the recommended pattern of determining the default Docker tag via the
appVersion
chart metadata, this only requires updatingappVersion
inChart.yaml
. Some charts cannot (or do not) do this, in which case the version has to be changed elsewhere, normally invalues.yaml
. Also update theversion
of the chart inChart.yaml
(which follows semantic versioning). When this PR is merged, a new chart will automatically be published. - If the chart version is pinned in Phalanx, update the chart version in
Chart.yaml
for the appropriate application under /services. IF the chart is not pinned, no Phalanx change is required.
This will tell Argo CD that the change is pending, but no changes are applied automatically.
You can now go to the /argo-cd
endpoint in the Rubin Science Platform deployment and sync the application.
You may need to click Refresh to see the updated version.
If the version of the chart is not pinned, you will need to use the arrow next to Refresh and choose Hard Refresh.
(You will need to click directly on the small arrow to see this option.)