Skip to content

Helm Chart Upgrade

This guide is meant for users of the chart that is installed on a system with a lower major version. As an example you upgrade from chart version 4.X to 5.X. Minor version upgrades are expect to use helm upgrade --install.

Upgrade steps for a major version

In general it is a good idea to test the upgrade procedure in your staging systems before executing it on production and do and a double check on the backups.

Validate your existing configuration

In case you get linting errors double check your configuration settings

helm lint ./ibexa-chart-x.x.x.tgz --with-subcharts -f myvalues.yaml

Option 1: Execute an upgrade via backup

  • Follow the backup guide
  • Run helm uninstall [release-name]. This will take your website down.
  • Delete all PV and PVC that have backup protection
  • Run helm upgrade --install as documented
  • Follow the restore guide
  • Your website is up again

On failure retry or recover from backup.

Option 2: Execute an in place upgrade

  • Follow the backup guide or own security
  • Run helm uninstall [release-name]. This will take your website down.
  • Delete PVs and PVCs that don't belong to mysql or ibexa storage
  • Remove the PVC from mysql and ibexa storage
  • Create PVCs for MySQL and Ibexa DXP storage manually and connect them to still existing PV. See adding a static storage volume for files
  • Add the storage.ExistingClaim configuration for the files PVC to your values.yaml.
  • Add the mysql.primary.persistence.existingClaim configuration for the MySQL PVC to your values.yaml.
  • Run helm upgrade --install as documented
  • Follow missing steps from the restore guide
  • Your website is up again

On failure retry or recover from backup.

Last update: February 13, 2023