Details

    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 100
    • 100% 100%
    • 0
    • 0

    Description

      Feature Overview

      Enable installation and lifecycle support of OpenShift 4 on VMware vSphere 8.

      Goals

      • Enable installation of OpenShift 4 on VMware vSphere 8 with all supported installation methods (e.g. UPI, IPI, Assisted Installer / Infrastructure Operator / ZTP).
      • OpenShift 4 on VMware vSphere 8 can be updated that results in a cluster and applications that are in a healthy state when update is completed.
      • Telemetry reports back on clusters using OpenShift 4 on vSphere 8 for connected OpenShift clusters.

       

      Problem

      • Currently, we only support deploying OpenShift 4 to VMware vSphere 6.x and 7.0. With the vSphere 8.0 being GAed in Sept 2022, customers will want to deployOpenShift to this new vSphere release.

       

      Why is this important

      • VMware vSphere is very popular among our install base. If we fail to provide support for this new version of vSphere, customers will look to move off of OpenShift and on to other technologies that provide support.
      • Note: VMware offers 7 years of support from the general availability of a new Major Release.

      Requirements

      • This Section:* A list of specific needs or objectives that a Feature must deliver to satisfy the Feature.. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts. If a non MVP requirement slips, it does not shift the feature.

       

      Requirement Notes isMvp?
      CI - MUST be running successfully with test automation This is a requirement for ALL features. YES
      Release Technical Enablement Provide necessary release enablement details and documents. YES

      (Optional) Use Cases

      This Section:

      • Main success scenarios - high-level user stories
      • Alternate flow/scenarios - high-level user stories
      • ...

      Questions to answer…

      • ...

      Out of Scope

      Background, and strategic fit

      This Section: What does the person writing code, testing, documenting need to know? What context can be provided to frame this feature.

      Assumptions

      • ...

      Customer Considerations

      • ...

      Documentation Considerations

      Questions to be addressed:

      • What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?
      • Does this feature have doc impact?
      • New Content, Updates to existing content, Release Note, or No Doc Impact
      • If unsure and no Technical Writer is available, please contact Content Strategy.
      • What concepts do customers need to understand to be successful in [action]?
      • How do we expect customers will use the feature? For what purpose(s)?
      • What reference material might a customer want/need to complete [action]?
      • Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available.
      • What is the doc impact (New Content, Updates to existing content, or Release Note)?

       

      Other

       
      Slack

       

       

      Attachments

        Issue Links

          Activity

            People

              racedoro@redhat.com Ramon Acedo
              julim Ju Lim
              Gregory Charot, Joel Speed, Joseph Callen, Richard Vanderpool, Shang Gao
              Joseph Callen Joseph Callen
              Shang Gao Shang Gao
              Stephanie Stout Stephanie Stout
              Senthamilarasu S Senthamilarasu S
              Votes:
              2 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: