Updating Portworx in your cluster

Beginning with version 2.12 Portworx uses an operator-based deployment model instead of the Helm based model use in version 2.11 and earlier. If you are updating from Portworx 2.11 to version 2.12, follow the migration steps in the Portworx documentation.

Looking to update Portworx in a Classic cluster? For more information, see Updating Classic worker nodes.

VPC: Updating worker nodes with Portworx volumes

Virtual Private Cloud

When you update a worker node in a VPC cluster, the worker node is removed from your cluster and replaced with a new worker node. If Portworx volumes are attached to the worker node that you replaced, you must attach the volumes to the new worker node.

Update only one worker node at a time. When the worker node update is complete, attach your Block Storage for VPC and restart the Portworx pod.

Enter maintenance mode on the worker nodes that you want to update.
Update your VPC worker nodes.
Attach raw Block Storage for VPC to your worker nodes.
Verify that your storage is attached by running the following command.
```
kubectl get pv -o yaml | grep "attachstatus"
```

Restart the Portworx pod on the new worker node.

kubectl delete pod <portworx_pod> -n <portworx_namespace>

Exit maintenance mode
```
pxctl service maintenance --exit
```
Mount the volume to your app.