v5.11.8

Fix database reconnection on transport error for API workers.

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

• v5.11.7
• v5.11.6

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.7.9 → 5.8.6 → 5.9.5, not 5.7.9 → 5.9.5.

Upgrade on GKE

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

Upgrade on EKS

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

Upgrade on LKE

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

Changelog

Bug fixes

Config API

• Enabled PostgreSQL database connection health checks between API worker tasks and their databases. Earlier, API workers experiencing network transport disruption wouldn't detect failer of the long-lived connection and reconnect. Logs showed a repetition of messages like psycopg.OperationalError: the connection is lost until service restart. Connection handling in the API itself wasn't affected.