Skip to content

v5.10.11

Improve tolerance for survivable pod failures during upgrades.

This release contains bug fixes to Hydrolix v5.10. Refer to the release notes to see other notable feature announcements and information for this version.

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.

Example:
Upgrade from 5.10.10 → 5.11.9 → 6.0.8, not 5.10.10 → 6.0.8.

Upgrade on GKE⚓︎

Upgrade on GKE
1
kubectl apply -f "https://www.hydrolix.io/operator/v5.10.11/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/v5.10.11/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/v5.10.11/operator-resources?namespace=$HDX_KUBERNETES_NAMESPACE"

Changelog⚓︎

Bug fixes⚓︎

Cluster operations⚓︎

  • Changed the backoffLimit from 0 to 6 for the init-cluster, init-turbine-api, check-bucket-access, and load-sample-project Kubernetes jobs to tolerate transient boot-time dependency races. The change prevents survivable single-pod failures from marking an entire upgrade as a failure.