Uploaded image for project: 'OpenShift Installer'
  1. OpenShift Installer
  2. CORS-3196

Provision GCP with CAPI (no mgmt cluster)

    XMLWordPrintable

Details

    • Epic
    • Resolution: Unresolved
    • Undefined
    • 4.16.0
    • None
    • None
    • GCP CAPI Install
    • False
    • None
    • False
    • Yellow
    • In Progress
    • OCPSTRAT-1006 - Remove Terraform from the GCP IPI installer
    • OCPSTRAT-1006Remove Terraform from the GCP IPI installer
    • 63
    • 63% 63%
    • Hide

      4/16/2024 - Yellow

      • Our focus is on following cards with the goal of getting successful CI run using CAPG
      • In conjuction with above we will be working on https://issues.redhat.com/browse/CORS-3252 in order to create the Internal LB in CAPG to support private clusters. Its not expected that these upstream changes will merge before Feature Freeze, they should merge before GA.
      • Work is continuing on the CI related cards in order to fully test this platform when the necessary PRs above have merged
      Show
      4/16/2024 - Yellow Our focus is on following cards with the goal of getting successful CI run using CAPG https://issues.redhat.com/browse/CORS-3260 , particularly the internal LB PR https://github.com/openshift/installer/pull/8151 CAPG upstream fix https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1207 needs to merged https://issues.redhat.com/browse/CORS-3447 In conjuction with above we will be working on https://issues.redhat.com/browse/CORS-3252 in order to create the Internal LB in CAPG to support private clusters. Its not expected that these upstream changes will merge before Feature Freeze, they should merge before GA. Work is continuing on the CI related cards in order to fully test this platform when the necessary PRs above have merged

    Description

      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

      • Provision GCP infrastructure without the use of Terraform

      Why is this important?

      • Removing Terraform from Installer

      Scenarios

      1. The new provider should aim to provide the same results as the existing GCP

      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 is running, tests are automated and merged.
      • 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>

      Attachments

        Issue Links

          Activity

            People

              bfournie@redhat.com Robert Fournier
              padillon Patrick Dillon
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: