Skip to content

v5.0.1

Bug fix

This release contains a bug fix that was applied to v5.0.0. Refer to the release notes for v5.0.0 to see other notable feature announcements and information.

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.0.1/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.0.1/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.0.1/operator-resources?namespace=$HDX_KUBERNETES_NAMESPACE"

Changelog⚓︎

General⚓︎

  • API
  • Fix an API response for summary table editing that should have generated a 400, but was generating a 500 response code.