Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-18637

Onboard CAPMetal3 into MCE 2.9

XMLWordPrintable

    • Onboard CAPMetal3 into MCE 2.9
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • Done
    • Hide
      May 30, 25
      Should be complete, waiting on confirmation that everything will work in Konflux
      Show
      May 30, 25 Should be complete, waiting on confirmation that everything will work in Konflux
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      In MCE 2.9.0, we plan to onboard the Cluster API Provider Metal3 as a subcomponent of MCE. This addition will enable users to deploy Cluster API-based clusters on bare metal infrastructure using Metal3.

      Why is this important?

      By integrating CAPMetal3 into MCE 2.9, users can now leverage the standardized Cluster API framework to automate the provisioning and lifecycle management of bare metal clusters.

      Scenarios

      The customer wants to provision a bare metal cluster. With the integration of CAPMetal3 in MCE 2.9, they can now deploy a Cluster API-based cluster directly on bare metal machines, streamlining infrastructure setup and enabling automated lifecycle management through Cluster API.

      Acceptance Criteria

      CAPMetal3 has been integrated into MCE 2.9 as a technology preview feature.

      Dependencies (internal and external)

      1. (Internal) Installer requires deployment images from the Build team.
      2. (External) Installer requires helm charts from CAPI team for CAPMetal3.

      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 - Doc issue opened with a completed template. Separate doc issue
        opened for any deprecation, removal, or any current known
        issue/troubleshooting removal from the doc, if applicable.
      • Considerations were made for Extended Update Support (EUS)

      Onboarding checklist

      Check-list to complete. (If not already complete, a Jira story or task should be created per item)

      • ✅Architecture Forum & Design Decision Review document approved
      • ❓Onboarding source code into Stolostron/repo
      • 🟢Build - Konflux
      • ⚠️Build - CPaaS?
      • ❓Meet ACM security code and image scanning
      • ❓Playbook
      • ⚠️Disconnected from Internet (installs / works in this mode)

       

      • 🟡Installer - Feature flag enabled/disabled
      • ⚠️FIPS readiness
      • ⚠️Infra Node support (install-to)
      • ⚠️Proxy support (OpenShift Global Proxy)

       

      • ⚠️QE
      • ⚠️Hub Backup / Restore compliance
      • ⚠️Hub Scale / Performance
      • ⚠️Global hub eventing

       

      • 🔴Documentation
      • ❓Threat Model
      • ⚠️Support Skills transfer
      • ⚠️Must-gather

      🔴🟡🟢❓🔍⚠️✅

              cwall@redhat.com Cameron Wall
              dbennett@redhat.com Disaiah Bennett
              Matthew Smigielski Matthew Smigielski
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: