Combined upgrade (InfoScale/Software and OpenShift Platform upgrade)

Last published : Jul 06, 2026
Note: Refer to this section if you plan to upgrade both software/InfoScale and the OpenShift platform together in a single rollout.
Combined upgrade allows users to merge a software upgrade with a platform upgrade (such as an OCP upgrade) into a single rollout. This process is highly recommended because it upgrades the InfoScale cluster stack and the underlying platform simultaneously, minimizing worker node reboots by requiring only one rollout instead of two.
To use this feature, standard pre-flight requirements for any upgrade must be met. Additionally, you should only opt for a combined upgrade if the target release matrix supports both the new InfoScale stack and the new platform’s kernel version; if the target kernel is not supported, you must perform a software upgrade first.
To perform a combined upgrade:
  1. Create the license secret by running: oc create secret generic infoscale-license -n infoscale-vtas --from-file=infoscale-license.lic=<license_file_location>.
  2. Upgrade the operator to the latest version before initiating any software or platform changes. Refer to InfoScale operator upgrade for more information.
  3. Patch the InfoScale cluster by setting the combine-upgrade parameter to enabled.
    Specify the target version (example, 9.2.0) within the cluster configuration.
    # oc patch infoscalecluster <cluster-name> -n infoscale-vtas
    --type=merge -p '{"metadata":{"annotations":{"infoscale.veritas.com/
    combine-upgrade":"enabled"}},"spec":{"version":"9.2.0"}}'

    # oc get infoscaleclusters -A

    NAMESPACE NAME VERSION CLUSTERID STATE
    infoscale-vtas sanity-ocp416 9.2.0 21432 Upgrading
    DISKGROUPS STATUS AGE
    vrts_kube_dg-21432 Healthy 13m
  4. Verify that the cluster state transitions to upgrade pending.
     NAMESPACE NAME VERSION CLUSTERID STATE
     infoscale-vtas sanity-ocp416 9.2.0 21432 OS-Upgrade-Pending

     DISKGROUPS         STATUS  AGE
     vrts_kube_dg-21432 Healthy 18m
  5. Initiate the upgrade of all common resources—such as fencing and CSI—under the infoscaleclusterset controller. Wait for the process to reach the
        NAME VERSION CLUSTERID
    infoscalecluster.infoscale.veritas.com/sanity-ocp416 9.2.0 21432
    STATE DISKGROUPS STATUS AGE
    OS-Upgrade-Pending vrts_kube_dg-21432 Degraded 38m
    NAME READY STATUS
    pod/infoscale-csi-controller-7989c8864c-qxr4d 5/5 Running
    pod/infoscale-csi-node-6z6ns 2/2 Running
    pod/infoscale-csi-node-7qz9c 2/2 Running
    pod/infoscale-csi-node-dxgnq 2/2 Running
    pod/infoscale-csi-node-jqbqt 2/2 Running
    pod/infoscale-csi-node-lbmrg 2/2 Running
    pod/infoscale-csi-node-rtjl7 2/2 Running
    pod/infoscale-fencing-controller-56dd955df9-f4rrx 1/1 Running
    pod/infoscale-fencing-enabler-5hqzm 1/1 Running
    pod/infoscale-fencing-enabler-7jlfj 1/1 Running
    pod/infoscale-fencing-enabler-bzmlf 1/1 Running
    pod/infoscale-fencing-enabler-md9qj 1/1 Running
    pod/infoscale-fencing-enabler-s66pw 1/1 Running
    pod/infoscale-fencing-enabler-tkltz 1/1 Running
    pod/infoscale-licensing-operator-ccf6b49dd-t86lg 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-22v6p 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-5swtc 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-8d8nz 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-c2lzj 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-kf5bb 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-m4qk6 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-w2dcx 1/1 Running
    pod/infoscale-sds-operator-7dc6df8c96-xkh94 1/1 Running
    RESTARTS AGE IP NODE NOMINATED NODE 0 22m 10.129.2.25 ocptest02-w02.eng.internal <none> 0 19m 10.128.4.27 ocptest02-w07.eng.internal <none> 0 17m 10.131.2.24 ocptest02-w05.eng.internal <none> 0 20m 10.129.4.73 ocptest02-w01.eng.internal <none> Upgrading InfoScale 117
    Combined upgrade
    0 21m 10.130.2.21 ocptest02-w04.eng.internal <none> 0 20m 10.128.2.25 ocptest02-w03.eng.internal <none> 0 18m 10.129.2.26 ocptest02-w02.eng.internal <none> 1 (20m ago) 38m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 38m 10.210.9.1 ocptest02-w04.eng.internal <none> 0 38m 10.210.8.242 ocptest02-w03.eng.internal <none> 0 38m 10.210.9.4 ocptest02-w07.eng.internal <none> 0 38m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 38m 10.210.9.2 ocptest02-w05.eng.internal <none> 0 38m 10.210.8.183 ocptest02-w02.eng.internal <none> 0 12h 10.128.2.19 ocptest02-w03.eng.internal <none> 0 38m 10.210.8.183 ocptest02-w02.eng.internal <none> 0 38m 10.210.9.1 ocptest02-w04.eng.internal <none> 0 38m 10.210.9.2 ocptest02-w05.eng.internal <none> 0 38m 10.210.9.4 ocptest02-w07.eng.internal <none> 0 38m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 38m 10.210.9.3 ocptest02-w06.eng.internal <none> 0 38m 10.210.8.242 ocptest02-w03.eng.internal <none> 0 23m 10.129.4.72 ocptest02-w01.eng.internal <none> ---
    [root@ocptest02-ba1 ~]# oc get ds -n infoscale-vtas
    NAME DESIRED CURRENT READY UP-TO-DATE
    infoscale-csi-node 7 7 7 7
    << up-to-date should match to InfoScale nodes
    infoscale-fencing-enabler 7 7 7 7
    infoscale-sds-21432-5b4fd1b149105b9b 7 7 7 7
    infoscale-sds-21432-f81a8a6c09e1b253 0 0 0 0
    AVAILABLE NODE SELECTOR 7 IS-cluster-node=true 7 IS-cluster-node=true 7 IS-cluster-name=sanity-ocp416,infoscale.veritas.com/
    kernel-version=5.14.0-427.106.1.el9_4.x86_64,infoscale.veritas.com/os-release=0
  6. Monitor the intermediate state that appears after the node rollout begins. Observe that a new DaemonSet is created as the SDS (Software Defined Storage) shifts from the old DaemonSet to the new one.
    NAME VERSION CLUSTERID
    infoscalecluster.infoscale.veritas.com/sanity-ocp416 9.2.0 21432
    STATE DISKGROUPS STATUS AGE
    OS-Upgrade-Pending vrts_kube_dg-21432 Degraded 97m
    NAME READY STATUS
    pod/infoscale-csi-controller-7989c8864c-slbsn 5/5 Running
    pod/infoscale-csi-node-6jnkn 2/2 Running
    pod/infoscale-csi-node-98qfg 2/2 Running
    pod/infoscale-csi-node-dxgnq 2/2 Running
    pod/infoscale-csi-node-jktzt 2/2 Running
    pod/infoscale-csi-node-pjk9c 2/2 Running
    pod/infoscale-csi-node-sdb2j 2/2 Running
    pod/infoscale-fencing-controller-56dd955df9-f4rrx 1/1 Running
    pod/infoscale-fencing-enabler-5xkhf 1/1 Running
    pod/infoscale-fencing-enabler-md9qj 1/1 Running
    pod/infoscale-fencing-enabler-n4t7q 1/1 Running
    pod/infoscale-fencing-enabler-pbtsc 1/1 Running
    pod/infoscale-fencing-enabler-rsdvj 1/1 Running
    pod/infoscale-fencing-enabler-xlc7c 1/1 Running
    pod/infoscale-licensing-operator-ccf6b49dd-2qjqn 1/1 Running
    pod/infoscale-sds-21432-5b4fd1b149105b9b-kf5bb 1/1 Running
    pod/infoscale-sds-21432-f81a8a6c09e1b253-6gwj5 1/1 Running
    pod/infoscale-sds-21432-f81a8a6c09e1b253-7ftc2 1/1 Running
    pod/infoscale-sds-21432-f81a8a6c09e1b253-mf8wz 1/1 Running
    pod/infoscale-sds-21432-f81a8a6c09e1b253-pksf6 1/1 Running
    pod/infoscale-sds-21432-f81a8a6c09e1b253-qd7jn 1/1 Running
    pod/infoscale-sds-operator-7dc6df8c96-xkh94 1/1 Running
    ---
    RESTARTS AGE IP NODE NOMINATED NODE 0 43m 10.128.2.14 ocptest02-w03.eng.internal <none> 0 20m 10.130.2.8 ocptest02-w04.eng.internal <none> 0 9m37s 10.131.2.9 ocptest02-w05.eng.internal <none> 0 79m 10.129.4.73 ocptest02-w01.eng.internal <none> Upgrading InfoScale 119
    Combined upgrade
    0 44m 10.128.2.8 ocptest02-w03.eng.internal <none> 0 30m 10.129.2.7 ocptest02-w02.eng.internal <none> 0 55m 10.131.0.6 ocptest02-w06.eng.internal <none> 1 (79m ago) 97m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 30m 10.210.8.183 ocptest02-w02.eng.internal <none> 0 97m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 9m36s 10.210.9.2 ocptest02-w05.eng.internal <none> 0 55m 10.210.9.3 ocptest02-w06.eng.internal <none> 0 44m 10.210.8.242 ocptest02-w03.eng.internal <none> 0 20m 10.210.9.1 ocptest02-w04.eng.internal <none> 0 54m 10.131.0.14 ocptest02-w06.eng.internal <none> 0 97m 10.210.8.175 ocptest02-w01.eng.internal <none> 0 9m36s 10.210.9.2 ocptest02-w05.eng.internal <none> 0 30m 10.210.8.183 ocptest02-w02.eng.internal <none> 0 20m 10.210.9.1 ocptest02-w04.eng.internal <none> 0 55m 10.210.9.3 ocptest02-w06.eng.internal <none> 0 44m 10.210.8.242 ocptest02-w03.eng.internal <none> 0 82m 10.129.4.72 ocptest02-w01.eng.internal <none> ---
    NAME DESIRED CURRENT SELECTOR
    daemonset.apps/infoscale-csi-node 6 6 rctera/ose-csi-node-driver-registrar-rhel9:v4.21 app=infoscale-csi-node
    daemonset.apps/infoscale-fencing-enabler 6 6 app=infoscale-fencing-enabler
    daemonset.apps/infoscale-sds-21432-5b4fd1b149105b9b 1 1 IS-cluster-name=sanity-ocp416,infoscale.veritas.com/kernel-version=5.14.0-4.x86_64 IS-cluster-name=sanity-daemonset.apps/infoscale-sds-21432-f81a8a6c09e1b253 5 5 IS-cluster-name=sanity-ocp416,infoscale.veritas.com/kernel-version=5.14.0-4.x86_64 IS
  7. Verify the final cluster state to ensure the old DaemonSet has been cleaned up and the cluster status is Healthy.
Related information