Upgrade to v5.4.0

Upgrade instructions

These are the same upgrade instructions from the release notes.

GKE upgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.4.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&gcp-storage-sa=${GCP_STORAGE_SA}"

EKS upgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.4.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&aws-storage-role=${AWS_STORAGE_ROLE}"

LKE upgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.4.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}"

v5.4.0 to v5.3.0 downgrade procedure

Downgrading Hydrolix from v5.4.0 to v5.3.0 is much like upgrading, with a schema migration rollback.

Overview

1. Perform the schema migration rollback
2. Perform the downgrade to v5.3.0

During the upgrade, several schema changes are applied automatically to support column aliasing and service accounts.

In order to downgrade, revert these schema changes first using these instructions.

Perform the schema migration rollback

The following steps restore the schema to the schema expected by v5.3.0.

1. Connect to the Kubernetes cluster using k9sand select the namespace holding the Hydrolix cluster.

2. Select the turbine-api pod and turbine-api container.

3. Invoke a shell, by entering s.

4. Execute each of the following commands, which will produce STDERR to terminal. Each must exit cleanly.

   Shell

   ./manage.py migrate service_accounts 0001
   ./manage.py migrate tables 0026
   ./manage.py migrate dictionaries 0005
   

Perform the downgrade to v5.3.0

GKE downgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.3.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&gcp-storage-sa=${GCP_STORAGE_SA}"

EKS downgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.3.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&aws-storage-role=${AWS_STORAGE_ROLE}"

LKE downgrade

kubectl apply -f "https://www.hydrolix.io/operator/v5.3.0/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}"