v6.1.7

Fix for VPA scaler on overscaled, never-scaled workloads. Optional, better node-capacity and workload fit checks.

This release contains a bug fix and an improvement for Hydrolix v6.1. For other feature announcements and details, see the earlier v6.1 release notes.

• v6.1.6
• v6.1.5

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.

Upgrade on GKE

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

Upgrade on EKS

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

Upgrade on LKE and AKS

kubectl apply -f "https://www.hydrolix.io/operator/v6.1.7/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}"

Changelog

Improvements

Cluster operations

• Improved hdx-scaler-go node-capacity awareness before it applies a VPA scaling decision. For DaemonSets it uses the minimum capacity across nodes; for Deployments it verifies the proposed scale fits on the largest schedulable node. These node-capacity checks are off by default in this release.

Bug fixes

Cluster operations fixes

• Corrected an hdx-scaler-go vertical pod autoscaling (VPA) bug in which an overscaled workload was never scaled down. Earlier, if no scaling event occurred, no scale-down event could occur. Fixed by requiring only a full horizon of observation to trigger the scale-down event.