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

RHACM on cloud infra (Azure/Google Cloud) deploying on premises bare metal clusters

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-10Install and update OpenShift on Infrastructure Providers
    • 0% To Do, 0% In Progress, 100% Done
    • 0

      Goal

      As an OpenShift hub cluster (RHACM/MCE) administrator, I want to deploy bare metal clusters from RHACM or MCE running on cloud infrastructure:

      • RHACM/MCE running on ARO
      • RHACM/MCE running on OpenShift on Azure
      • RHACM/MCE running on OpenShift on Google Cloud

      Why is this important

      We have customer requirements to allow ACM deploying bare metal clusters from hyperscalers. This will allow customers to manage their clusters centrally from cloud infrastructure. For example Poste Italiane wants to have their hub cluster in a hyperscaler and deploy from it OpenShift clusters on premises in their post offices across the country.

      This aligns with our strategy for the open hybrid cloud, enabling any workload, on any footprint in any location. This also will enable customers to keep extending their edge presence anywhere while centrally managing their clusters.

      This solution is also superior to AWS EKS Anywhere for bare metal, where AWS now allows deploying on-prem bare metal clusters, although they can't be managed from AWS., and this is a true open hybrid cloud solution (EKS Anywhere would be somewhere between the Agent-Based Installer and this solution).

       Acceptance Criteria

      • Bare metal worker nodes can be deployed from a hub cluster running ACM in the Central Infrastructure Management workflow as a day 2 operation from Azure/ARO/Google Cloud.
      • It is possible to interact with the Metal3 BaremetalHost API to provision baremetal hosts from a non-baremetal controlplane
      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.

              racedoro@redhat.com Ramon Acedo
              racedoro@redhat.com Ramon Acedo
              Pedro Jose Amoedo Martinez Pedro Jose Amoedo Martinez
              Daniel Macpherson Daniel Macpherson
              Zane Bitter Zane Bitter
              Jean-Francois Saucier Jean-Francois Saucier
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: