Upgrade Portworx using Helm on FlashArray and OCP vSphere

This page provides instructions on how to upgrade Portworx using Helm.

note

Upgrading from a previous Portworx Helm chart version to 4.0.0 is not supported.

Prerequisites

• You must have installed Portworx using Helm.
• Review the release notes for the version you plan to upgrade to. This ensures you are aware of any breaking changes, new features, and deprecated configurations.
  • Portworx Enterprise Release Notes
  • Portworx Operator Release Notes
  • Portworx Stork Release Notes
  • Portworx Autopilot Release Notes
• Review the Helm compatibility matrix and the configurable parameters.

Upgrade Portworx

note

During an upgrade, Portworx pods are deleted and re-created on each node to apply the spec changes. The spec.updateStrategy field in the StorageCluster resource controls how nodes are upgraded. By default, the update strategy is RollingUpdate, and the maxUnavailable field specifies the maximum number of nodes that can be unavailable at a time. The default value of maxUnavailable is 1.

This is expected behavior, and you might see pod deletion events in the Kubernetes audit logs. You don't need to take any action.

By default, Portworx is installed in the kube-system namespace. If you have installed it in a different namespace, use the -n <namespace> flag. In this example, you upgrade the Portworx installation in the portworx namespace.

1. Download the latest Portworx Helm chart version from the portworx/helm repository to your local repository:

   helm repo update

   Hang tight while we grab the latest from your chart repositories...
   ...Successfully got an update from the "portworx" chart repository
   Update Complete. ⎈Happy Helming!⎈

2. If you installed Portworx with custom configuration and need to change any configuration parameters, update your px_install_values.yaml file.

   note

   Ensure that you review the configuration values for the new version to align with any changes in the latest release.

3. Upgrade Portworx using the following command:

   helm upgrade <px-release> portworx/portworx -n <portworx> -f px_install_values.yaml

   Release "px-release" has been upgraded. Happy Helming!
   NAME: px-release
   LAST DEPLOYED: Thu Sep 26 06:51:46 2024
   NAMESPACE: portworx
   STATUS: deployed
   REVISION: 3
   TEST SUITE: None
   NOTES:
   Your Release is named "px-release"
   Portworx Pods should be running on each node in your cluster.
   
   Portworx creates a unified pool of the disks attached to your Kubernetes nodes. 
   No further action should be required and you are ready to consume Portworx Volumes as part of your application data requirements. 

4. Verify the Helm release values to ensure they reflect the updated configuration:

   helm get values <px-release> -n <portworx>

   You should see all the custom configurations passed using the px_install_values.yaml file.