• False
    • Hide


    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 0% To Do, 0% In Progress, 100% Done
    • 0
    • 0

      Feature Overview (aka. Goal Summary)  

      In 4.13 the vSphere CSI migration is in hybrid state. Greenfield 4.13 clusters have migration enabled by default while upgraded clusters have it turned off unless explicitely enabled by an administrator (referred as "opt-in").

      This feature tracks the final work items required to enable vSphere CSI migration for all OCP clusters.

      More information on the 4.13 vSphere CSI migration is available in the internal FAQ

      Goals (aka. expected user outcomes)

      Finalise vSphere CSI migration for all clusters ensuring that

      • Greenfield 4.14 clusters have migration enabled
      • Enable migration on clusters upgraded from 4.13 (for those that have it disable)
      • Enable migration on cluster upgraded from 4.14.
      • Disable the 4.13 featureset that allowed admins to opt in migration

      Regardless of the clusters state (new or upgraded), which version it is upgrading from or status of CSI migration (enabled/disabled), they should all have CSI migration enabled.

      This feature also includes upgrades checks in 4.12 & 4.13 to ensure that OCP is running on a recommended vSphere version (vSphere 7.0u3L+ or 8.0u2+)

      Requirements (aka. Acceptance Criteria):

      We should make sure that all issues that prevented us to enabled CSI migration by default in 4.13 are resolved. If some of these issues are fix in vSphere itself we might need to check for a certain vSphere build version before proceeding with the upgrade (from 4.12 or 4.13).


      Use Cases (Optional):

      • New 4.14 clusters
      • Clusters upgraded from 4.13 with migration enabled
      • Clusters upgraded from 4.13 with migration disabled
      • Clusters upgraded from 4.12 (migration disabled)



      More information on the 4.13 vSphere CSI migration is available in the internal FAQ

      Customer Considerations

      Customers who upgraded from 4.12 will unlikely opt in migration so we will have quite a few clusters with migration enabled. Given we will enabled it in 4.14 for every clusters we need to be extra careful that all issues raised are fixed and set upgrade blockers if needed.

      Documentation Considerations

      Remove all migration opt-in occurences in the documentation.

      Interoperability Considerations

      We need to make sure that upgraded clusters are running on top of a vsphere version that contains all the required fixes.

            jdobson@redhat.com Jonathan Dobson
            rh-gs-gcharot Gregory Charot
            Hemant Kumar
            Rohit Patil Rohit Patil
            Lisa Pettyjohn Lisa Pettyjohn
            Gregory Charot Gregory Charot
            Eric Rich Eric Rich
            1 Vote for this issue
            14 Start watching this issue