Skip to content

v6.1.8

Remove a cluster initialization backup job that's no longer required.

Upgrade⚓︎

Don't skip minor versions when upgrading or downgrading

Skipping versions when upgrading or downgrading Hydrolix can result in database schema inconsistencies and cluster instability. Always upgrade or downgrade sequentially through each minor version, moving to every intermediate minor release in turn rather than jumping directly from the starting version to the target.

Upgrade on GKE⚓︎

Upgrade on GKE
1
kubectl apply -f "https://www.hydrolix.io/operator/v6.1.8/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&gcp-storage-sa=${GCP_STORAGE_SA}"

Upgrade on EKS⚓︎

Upgrade on EKS
1
kubectl apply -f "https://www.hydrolix.io/operator/v6.1.8/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}&aws-storage-role=${AWS_STORAGE_ROLE}"

Upgrade on LKE⚓︎

Upgrade on LKE
1
kubectl apply -f "https://www.hydrolix.io/operator/v6.1.8/operator-resources?namespace=$HDX_KUBERNETES_NAMESPACE"

Changelog⚓︎

Bug fixes⚓︎

Cluster operations⚓︎

  • Removed cluster initialization dependency on an additional backup job for Keycloak data. The job and data provided a safety mechanism during a major Keycloak version upgrade as a part of the Hydrolix v5.7 release. The Keycloak data are backed up as a part of PostgreSQL database backups.