Upgrade

We recommended that you only change values you need to customize in your values.yml file to ensure smooth upgrading. Always check the upgrading instructions between chart versions.

Upgrading the chart

When upgrading Horizon, you’ll need to pull the latest version of the chart:

$ helm repo update evertrust

Verify that you now have the latest version of Horizon (through the App version column):

$ helm search repo evertrust/horizon
NAME                       	CHART VERSION	APP VERSION	DESCRIPTION
evertrust/horizon          	0.5.3        	2.2.2      	EverTrust Horizon Helm chart

Launch an upgrade by specifying the new version of the chart through the --version flag in your command :

$ helm upgrade <horizon> evertrust/horizon \
 --values override-values.yaml \
 --version 0.5.3

The chart will automatically create a Job that runs an upgrade script when it detects that the Horizon version has changed between two releases. If the upgrade job fails to run, check the job’s pod logs. When upgrading from an old version of Horizon, you may need to explicitly specify the version you’re upgrading from using the upgrade.from key.

Before upgrading to specific chart version, thoroughly read any Specific chart upgrade instructions for your version.

Specific chart upgrade instructions

Upgrading to 0.3.0

  • Loggers are now configured with an array instead of a dictionary. Check the values.yaml format and update your override values.yaml accordingly.

  • The init dabatabase parameters (initDatabase, initUsername and initPassword) have been renamed and moved to mongodb.horizon.

Upgrading to 0.5.0

  • The ingress definition has changed. The rules and tls keys have been removed in favor of a more user-friendly hostname that will autoconfigure the ingress rules, and a boolean tls key that will enable TLS on that ingress. Check the Ingress section.