Upgrade Portworx on Kubernetes using the Operator in AKS
If you're using the Portworx Operator, you can upgrade or change your Portworx version at any time by modifying the StorageCluster
spec.
In addition to managing a Portworx cluster, the Operator also manages the following other components in the Portworx platform:
- Stork
- Autopilot
For simplicity, the Portworx Operator handles the component upgrades without user intervention. When Portworx upgrades, the Operator upgrades the installed components to the recommended version as well.
Prerequisites
- You must already be running Portworx through the Operator, this method will not work for other Portworx deployments.
- You must be running the latest available version of the Operator.
- For an air-gapped environment, complete the instructions in the Get the updated container images section.
Upgrade Portworx
If using configmap, update the version manifest for Portworx Operator. Otherwise, you might not see the expected image versions.
-
Enter the
kubectl get
command to identify your storage cluster name:kubectl get storagecluster -n <px-namespace>
NAME CLUSTER UUID STATUS VERSION AGE
px-cluster-xxxxxxxx-xxxx-xxxx-xxxx-0477837b54c7 xxxxxxxx-xxxx-xxxx-xxxx-7b4739f27cf3 Online 2.10.3 43d -
Enter the
kubectl edit
command to modify your storage cluster:kubectl edit storagecluster -n <px-namespace> <storagecluster-name>
Change the
spec.image
value to the version you want to update Portworx to:apiVersion: core.libopenstorage.org/v1
kind: StorageCluster
metadata:
name: portworx
namespace: <px-namespace>
spec:
image: portworx/oci-monitor:<your-desired-version>storagecluster.core.libopenstorage.org/px-cluster-xxxxxxxx-xxxx-xxxx-xxxx-0477837b54c7 edited
noteTo look up recent versions, refer to the Portworx release notes
-
Verify your upgrade using
kubectl get
command and make note of the version displayed underVERSION
.kubectl get storagenodes -n <px-namespace> -l name=portworx
"NAME ID STATUS VERSION AGE",
"node-1-1 xxxxxxxx-xxxx-xxxx-xxxx-06c81b607226 Online 2.11.3-8a0b7a8 10d",
"node-1-2 xxxxxxxx-xxxx-xxxx-xxxx-cf8908228900 Online 2.11.3-8a0b7a8 10d",
"node-1-3 xxxxxxxx-xxxx-xxxx-xxxx-c3239f8428d6 Online 2.11.3-8a0b7a8 10d"noteFor air-gapped clusters, if you do not see the expected image versions that you have configured in the configmap, you should edit the StorageCluster to include the
autoUpdateComponents: Once
parameter. This will force Portworx Operator to reconcile all the components and retrieve the correct images.