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

CAPO is functionally equivalent to what installer/terraform did pre 4.16

XMLWordPrintable

    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • 100% To Do, 0% In Progress, 0% Done
    • 0
    • Backlog Refinement

      Note: this used to be an EPIC that is now a Feature due to its large scope.

      Goal

      • Remove any workarounds existent on the installer to support scenarios like, failure domains, security groups, server groups and API load-balancing.
      • It is possible to install OpenShift on OpenStack using only CAPO.
      • The integration supports all deployment scenarios which are currently supported by openshift installer.

      Why is this important?

      • Intermediate, testable deliverable.
      • Direct requirement for installer integration.
      • Like TechPreview equivalent, we do not intend to support this functionality independent of the installer.

      Scenarios

      • User installs OpenShift with CAPO enabled.
      • User deploys CAPI templates in a private namespace which deploy OpenShift on OpenStack.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions::

      1. ...

              grosenbe-redhat.com Gil Rosenberg
              emacchi@redhat.com Emilien Macchi
              Stephanie Stout Stephanie Stout
              Jon Thomas Jon Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: