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

[Tech Preview] Provision GCP with CAPI (no mgmt cluster)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.16.0
    • None
    • None
    • GCP CAPI Install
    • False
    • None
    • False
    • Green
    • Done
    • OCPSTRAT-1006 - [Tech Preview] Remove Terraform from the GCP IPI installer
    • OCPSTRAT-1006[Tech Preview] Remove Terraform from the GCP IPI installer
    • 3% To Do, 3% In Progress, 94% Done
    • Hide

      5/10/2024 - Green for TechPreview

      Show
      5/10/2024 - Green for TechPreview All necessary PRs have merged CI passes with a minimal installation - the altinfra-e2e-gcp-capi-ovn test with https://github.com/openshift/installer/pull/8386 . The main functionality we will be missing is the Internal PublishingStrategy, aka PrivateClusters support along with SharedVPC support. These both have upstream PRs which are waiting review - https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1189 and https://github.com/kubernetes-sigs/cluster-api-provider-gcp/pull/1222 . We still need to merge a fix to use feature gate specific to CAPG.

      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):

      1. …

      Open questions::

      1. …

      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>

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

              Created:
              Updated:
              Resolved: