Skip to content

v5.4.5

Bug fix for Kafka TLS source not connecting to server

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

Upgrade⚓︎

Do not 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.5.0 → 5.6.x → 5.7.4, not 5.5.0 → 5.7.4.

Upgrade on GKE⚓︎

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

Upgrade on EKS⚓︎

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

Upgrade on LKE⚓︎

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

Changelog⚓︎

Bug Fix⚓︎

Intake⚓︎

  • Fixed an issue where a cluster with a Kafka source without a related credential caused the kafka-peer to emit an error to the log:
1
{"error":"failed to retrieve credential : credential  not found","file":"kafka_source.go:407","level":"error","message":"Unable to authenticate Kafka connection.","timestamp":"2025-09-22T16:57:52.409+00:00"}

The behavior now uses the cluster's credentials if other credentials are omitted, and no error is logged.