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

Installer updates for Custom DNS when installed with GCP CAPI(CAPG)

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 4.18.0
    • 4.18.0
    • openshift/installer
    • None
    • Installer updates for Custom DNS when installed with GCP CAPI(CAPG)
    • BU Product Work
    • False
    • None
    • False
    • Green
    • In Progress
    • OCPSTRAT-990 - [GA] Allow customer managed DNS solutions for GCP: Implementation
    • OCPSTRAT-990[GA] Allow customer managed DNS solutions for GCP: Implementation
    • 43% To Do, 0% In Progress, 57% Done
    • Hide

      11/19/2024 - 2 PRs left waiting to merge with all the required labels then can move to dev-complete

      10/15/2024 - Green - Completed re-implementing installer functionality to add LB IP addresses to Infra CR and bootstrap Ignition after move to CAPI based installs. In the process of adding techpreview CI job for this functionality.

      Show
      11/19/2024 - 2 PRs left waiting to merge with all the required labels then can move to dev-complete 10/15/2024 - Green - Completed re-implementing installer functionality to add LB IP addresses to Infra CR and bootstrap Ignition after move to CAPI based installs. In the process of adding techpreview CI job for this functionality.

      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

      • Update Installer changes to accompany the move to Installation with CAPG

      Why is this important?

      • https://issues.redhat.com/browse/CORS-2460 was completed when installation on GCP was completed using terraform. Now, with the removal of terraform based installation and move to CAPI based installation, some of the previously completed tasks need to be revisited-re-implemented.

      Scenarios

      1. ...

      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>

              sdasu@redhat.com Sandhya Dasu
              sdasu@redhat.com Sandhya Dasu
              Jianli Wei Jianli Wei
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: