Skip to content

v6.0.9

Fixed a memory leak, added startup and liveness probes to intake-router, recycled stale database connections, and added retries with backoff for initialization jobs.

This release contains bug fixes to Hydrolix v6.0. 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/v6.0.9/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.0.9/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.0.9/operator-resources?namespace=$HDX_KUBERNETES_NAMESPACE"

Changelog⚓︎

Improvements⚓︎

Operator improvements⚓︎

  • The intake-router now serves the standard grpc.health.v1.Health service on its existing gRPC port, reporting SERVING once the server is up. Startup and liveness gRPC probes have been added to the intake-router deployment. A reusable grpc_probe helper is now available for defining Kubernetes gRPC probes.

  • The init-cluster, init-turbine-api, check-bucket-access, and load-sample-project initialization jobs now use a backoffLimit of 6 instead of 0. Transient, recoverable failures such as dependency boot races during an upgrade now retry for roughly 15 to 20 minutes rather than failing on the first pod error.

Bug fixes⚓︎

Core bug fixes⚓︎

  • Fixed a core memory leak. An internal queue is now periodically drained, releasing the memory it held.

Config API bug fixes⚓︎

  • Stale worker database connections are now recycled so tasks no longer reuse connections that are invalid. Connection handling was also corrected for tasks that run synchronously or inside an atomic transaction.