Skip to content

v5.10.12

Tighten Kubernetes roles and role bindings for the workload reloader.

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, moving to every intermediate minor release in turn rather than jumping directly from the starting version to the target.

Point releases are safe to skip. Upgrade through each minor version, using the latest point release of each one. Don't install every point release along the way.

For example, to go from v5.10 to v6.1, upgrade sequentially to v5.11.10 -> v6.0.19 -> v6.1.10. Downgrading works the same way, in reverse.

Upgrade on GKE⚓︎

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

Upgrade on EKS⚓︎

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

Upgrade on LKE⚓︎

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

Changelog⚓︎

Bug fixes⚓︎

Cluster operations⚓︎

  • Kubernetes RBAC roles and bindings for the reloader weren't constrained. While it never triggered rollouts in other namespaces, now it has permissions only to the deployment's namespace. This change also similarly tightened roles and bindings for the scheduler, descheduler, and otel workloads.