Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-1005

Remove Terraform from the Azure Stack Hub IPI installer

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      This feature is no longer blocked on epic CORS-3061. CORS-3061 is currently dev-complete with testing in progress. This feature is currently unblocked.

      Based on status summary in epic CORS-3061, it's unable to get successful installation with minimal configuration so far, dev is working on it.

      Show
      This feature is no longer blocked on epic CORS-3061 . CORS-3061 is currently dev-complete with testing in progress. This feature is currently unblocked. Based on status summary in epic CORS-3061 , it's unable to get successful installation with minimal configuration so far, dev is working on it.
    • False
    • OCPSTRAT-911De-risk Terraform dependency in Installer
    • 33% To Do, 33% In Progress, 33% Done
    • M
    • 0
    • Backlog Refinement

      Feature Overview (aka. Goal Summary)

      As a result of Hashicorp's license change to BSL, Red Hat OpenShift needs to remove the use of Hashicorp's Terraform from the installer – specifically for IPI deployments which currently use Terraform for setting up the infrastructure.

      To avoid an increased support overhead once the license changes at the end of the year, we want to provision Azure Stack Hub infrastructure without the use of Terraform.

      Requirements (aka. Acceptance Criteria):

      • The Azure Stack Hub IPI Installer no longer contains or uses Terraform.
      • The new provider should aim to provide the same results and have parity with the existing Azure Stack Hub Terraform provider. Specifically, we should aim for feature parity against the install config and the cluster it creates to minimize impact on existing customers' UX.

      Use Cases (Optional):

      Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.

      Questions to Answer (Optional):

      Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

      Out of Scope

      High-level list of items that are out of scope. Initial completion during Refinement status.

      Background

      Provide any additional context is needed to frame the feature. Initial completion during Refinement status.

      Customer Considerations

      Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.

      Documentation Considerations

      Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

      Interoperability Considerations

      Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.

              mak.redhat.com Marcos Entenza Garcia
              julim Ju Lim
              Beth White, Joel Speed, Ju Lim, Mike Worthington, Patrick Dillon, Subin M, Vince Prignano (Inactive), Zane Bitter
              Patrick Dillon Patrick Dillon
              Gaoyun Pei Gaoyun Pei
              Stephanie Stout Stephanie Stout
              Patrick Dillon Patrick Dillon
              Patrick Dillon Patrick Dillon
              Marcos Entenza Garcia Marcos Entenza Garcia
              Eric Rich Eric Rich
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: