Skip to content

Upgrade to v6.1

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.

Overview⚓︎

The v6.1 release is the first in a sequence of releases installing support for multiple organizations in a Hydrolix cluster.

Special upgrade instructions⚓︎

Upgrade steps⚓︎

Step 1: Set tunable⚓︎

Set the tunable turbine_api_feature_migrate_projects_to_orgs to true if you want each of the projects in the cluster to be elevated to its own organization, or skip this step and accept the default.

1
2
spec:
  turbine_api_feature_migrate_projects_to_orgs: false

Default behavior: For a single-tenant cluster, after upgrading to v6.1, three Customer objects are created. One Customer object each is created for the projects hydro and sample_project. All other projects are associated with a third Customer object.

This is an example of explicit declaration of the default setting.

1
2
spec:
  turbine_api_feature_migrate_projects_to_orgs: true

Set this for multi-tenant clusters. This tunable must be explicitly set in the Hydrolix cluster spec before upgrading to v6.1.

A distinct Customer object is created for every existing project.

The tunable setting controls a background job that creates the parallel hierarchy and runs for the lifetime of Hydrolix v6.1.

Step 2: Apply new operator⚓︎

Select the appropriate command based on your cloud provider:

GKE:

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

EKS:

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

LKE and AKS:

1
kubectl apply -f "https://www.hydrolix.io/operator/vX.Y.z/operator-resources?namespace=${HDX_KUBERNETES_NAMESPACE}"

Step 3: Monitor upgrade progress⚓︎

Kubernetes jobs named init-cluster and init-turbine-api will automatically run to upgrade your entire installation to match the new operator's version number. This will take a few minutes, during which time you can observe your pods' restarts with your Kubernetes monitor tool.

Ensure both the init-cluster and init-turbine-api jobs have completed successfully and that the turbine-api pod has restarted without errors. After that, view the UI and use the API of your new installation as a final check.

If the turbine-api pod doesn't restart successfully, or other functionality is missing, check the logs of the init-cluster and init-turbine-api jobs for details about failures. This can be done using the k9s utility or with the kubectl command:

1
2
% kubectl logs -l app=init-cluster
% kubectl logs -l app=init-turbine-api

Contact Hydrolix Support at support@hydrolix.io for additional assistance.