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 Stream, you’ll need to pull the latest version of the chart :

$ helm repo update evertrust

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

$ helm search repo evertrust/stream
NAME                       	CHART VERSION	APP VERSION	DESCRIPTION
evertrust/stream          	0.2.0        	2.0.0      	EverTrust Stream Helm chart

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

$ helm upgrade stream evertrust/stream \
 --values override-values.yaml \
 --version 0.2.0

The chart will automatically create a Job that runs an upgrade script when it detects that the Stream 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 Stream, 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

Upgrade to 1.7.0

  • Switching to native Kubernetes leases implementation. CRDs leases aren’t used anymore.

Upgrade to 2.0.0

  • This version drops support for the Bitnami MongoDB subchart. Instead, a new temporaryDatabase key controls whether a temporary MongoDB instance should be created for the duration of the upgrade. To migrate from the Bitnami MongoDB subchart to a temporary instance or an external MongoDB database, you can use the mongodump and mongorestore utilities.