Method A: Basic Helm Upgrade
Audience: System Administrators
Content Summary: This guide outlines the basic method for upgrading Helm installations of Immuta in Kubernetes.
This method is typically acceptable when moving between minor point releases of Immuta (such as
2.7.1). Method B is a more involved method that leverages a full backup and restore procedure. Method B is needed when conducting more significant upgrades such as major releases (e.g.,
2.7.x), when making large jumps in versions (for example going from
2.7.x), or simply whenever advised by your Immuta professional.
Backup and Restore Upgrade Required for 2021.2
Postgres has been upgraded to Postgres 12, so you must do a complete back-up and restore upgrade for this release.
Ensure that you have updated your local Helm Chart before you complete the steps in this guide.
After you make any desired changes in your
immuta-values.yaml file, you can apply these changes
helm upgrade <YOUR RELEASE NAME> immuta/immuta \ --values immuta-values.yaml --version <YOUR DESIRED CHART VERSION>
helm upgrade immuta/immuta \ --values immuta-values.yaml \ --name <YOUR RELEASE NAME> \ --version <YOUR DESIRED CHART VERSION>
Note: Errors in upgrades can result when upgrading Chart versions on the installation. These are typically easily
resolved by making slight modifications of your values to accommodate the changes in the Chart. Downloading an
updated copy of the
immuta-values.yaml and comparing to your existing values is often a great way to debug
If you are on Kubernetes 1.22+, remove
upgrading; otherwise, your ingress service may not start after the upgrade.