Version: 26.2

Upgrade

Upgrading Authorization Hub involves a standard Helm chart upgrade. Follow the steps below to perform an upgrade:

note

For an environment without internet access, read the Upgrade section of the air-gapped deployment instead.

Back up your external PostgreSQL database by creating a snapshot or backup through your provider (AWS RDS, Azure SQL, etc.).
Download the latest Authorization Hub distribution.

tip
Read the Preparation section for details.
(Upgrading from a version earlier than 26.2) Create the redis secret. Starting with version 26.2, Authorization Hub stores user sessions in Redis, which the Helm chart deploys in your cluster and which requires a password. Skip this step if the secret already exists.
```
kubectl create secret generic redis \
  --from-literal=password=$CHANGE_ME
```
Replace $CHANGE_ME with a strong, randomly generated password.

warning
Create the secret before running the upgrade. The Redis pods and the API gateway cannot start without it.
Navigate to kubernetes/charts and upgrade the Helm chart.
```
helm upgrade hub \
-f hub/values.yaml hub \
--set registry=748131003707.dkr.ecr.eu-central-1.amazonaws.com/axiomatics/ \
--set hubHostname=$CHANGE_ME \
--set 'imagePullSecrets[0].name=regcred'
```
Replace $CHANGE_ME with your Authorization Hub hostname.

note
Sessions created before the upgrade are not carried over to Redis, so users must sign in again after the upgrade.
(Optional) If your load balancer was configured with sticky sessions for Authorization Hub, you can disable them after the upgrade. Sessions are now shared between all API gateway pods through Redis, so sticky sessions are no longer required. Read Session storage for details.