Skip to main content
Version: 3.1

Operator OpenShift upgrade path

info
Portworx by Pure Storage recommends upgrading the Portworx version prior to upgrading your OpenShift version.

Portworx 3.1.1

This upgrade path was tested with Portworx 3.1.1 and Operator 23.10.5.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.114.11.581.24.16
stable-4.124.12.511.25.16
stable-4.134.13.361.26.13
stable-4.144.14.151.27.10

Portworx 3.1.0

This upgrade path was tested with Portworx 3.1.0 and Operator 23.10.2.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.114.11.531.24.16
stable-4.124.12.441.25.14
stable-4.134.13.331.26.9

Portworx 3.0.0

This upgrade path was tested with Portworx 3.0 and Operator 23.5.1.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.104.10.611.23.17
stable-4.114.11.421.24.14
stable-4.124.12.201.25.10
stable-4.134.13.01.26.5

Portworx 2.13.0

This upgrade path was tested with Portworx 2.13.0 and Operator 1.10.4.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.94.9.551.22.15
stable-4.104.10.511.23.12
stable-4.114.11.261.24.6

Portworx 2.12.0

This upgrade path was tested with Portworx 2.12.0 and Operator 1.10.0.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.64.6.561.19.16
stable-4.74.7.591.20.15
stable-4.84.8.501.21.11
stable-4.94.9.491.22.8
stable-4.104.10.351.23.5
stable-4.114.11.81.24.0

Portworx 2.11.0

This upgrade path was tested with Portworx 2.11.0 and Operator 1.8.0.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.64.6.561.19.16
stable-4.74.7.591.20.15
stable-4.84.8.501.21.11
stable-4.94.9.491.22.8
stable-4.104.10.351.23.5
stable-4.114.11.81.24.0

Portworx 2.10.0

This upgrade path was tested with Portworx 2.10.0 and Operator 1.8.0.

note

If you are not on the same OCP version as in the tested upgrade example shown below, please upgrade to the next available version that is used in the upgrade path and continue as shown in the table below.

Channel versionOpenShift versionKubernetes version
stable-4.64.6.56v1.19.16+6175753
stable-4.74.7.45v1.20.14+0d60930
stable-4.84.8.35v1.21.8+ee73ea2
force 4.914.9.24v1.22.5+5c84e52
fast-4.104.10.6v1.23.5+b0357ed

  1. The upgrade hop to 4.9 was not publicly available via stable, fast, or candidate channels. --force --allow-explicit-upgrade --allow-upgrade-with-warnings was used to bypass this blocker for testing.
Was this page helpful?