Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-1454

Remove IPI/UPI support of Alibaba cloud from OpenShift

    • Remove IPI/UPI support of Alibaba cloud from OpenShift
    • Proactive Architecture
    • 30
    • False
    • None
    • False
    • Red
    • In Progress
    • OCPSTRAT-1466[Tech Debt] Finalize removal of Alibaba Cloud component removal
    • 58% To Do, 8% In Progress, 33% Done
    • L
    • Hide

      C/I/T: 12/12/30

      Show
      C/I/T: 12/12/30

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • We want to remove official support for UPI and IPI support for Alibaba Cloud provider. Going forward, we are recommending installations on Alibaba Cloud with either external platform or agnostic platform installation method.

      Why is this important?

      An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

      We have decided to remove IPI and UPI support for Alibaba Cloud, which until recently has been in Tech Preview due to the following reasons:

      (1) Low customer interest of using Openshift on Alibaba Cloud

      (2) Removal of Terraform usage

      (3) MAPI to CAPI migration

      (4) CAPI adoption for installation (Day 1) in OpenShift 4.16 and Day 2 (post-OpenShift 4.16)

      Scenarios

      Impacted areas based on CI:

      alibaba-cloud-csi-driver/openshift-alibaba-cloud-csi-driver-release-4.16.yaml
      alibaba-disk-csi-driver-operator/openshift-alibaba-disk-csi-driver-operator-release-4.16.yaml
      cloud-provider-alibaba-cloud/openshift-cloud-provider-alibaba-cloud-release-4.16.yaml
      cluster-api-provider-alibaba/openshift-cluster-api-provider-alibaba-release-4.16.yaml
      cluster-cloud-controller-manager-operator/openshift-cluster-cloud-controller-manager-operator-release-4.16.yaml
      machine-config-operator/openshift-machine-config-operator-release-4.16.yaml

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      Done Checklist

      • CI - CI jobs are removed
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

            jcallen@redhat.com Joseph Callen
            rhn-support-rvanderp Richard Vanderpool
            Jianli Wei Jianli Wei
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: