Upgrading Nexus Repository in an HA Environment
NEW IN 3.50.0
Upgrading Sonatype Nexus Repository in an HA environment does require downtime. Upgrade is not possible without downtime.
Do not add new instances until old instances are completely terminated.
Upgrading Using YAMLs (Without Helm Chart)
replicasto "0" using the command below:
kubectl get statefulsets <stateful-set-name> kubectl scale statefulsets <stateful-set-name> --replicas=0
Update the statefulsets.yaml with the Sonatype Nexus Repository version to wish you which to upgrade. Look for a line like the following:
- Ensure the statefulset.yaml is set to include the desired number of
Apply the updated statefulset.yaml:
kubectl apply -f <updated-stateful-set-file>
Upgrading Using Helm Charts
Uninstall the Helm chart using a command like the following where
<release-name>is the string you provided when first installing the chart:
helm uninstall <release-name>
Update the values.yaml to the desired Sonatype Nexus Repository version and number of replicas. Look for a line like the following:
container: image: repository: sonatype/nexus3 tag: <version-number>
Re-install the Helm chart using a command like the following:
helm install <release-name> --debug
Upgrading in a Non-Kubernetes Environment
If you are not using Kubernetes, you will need to stop each Sonatype Nexus Repository instance before upgrading.
Then, you can upgrade each instance following the instructions provided in Upgrading a Standalone Instance.