Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8431

RHACM: Enable Full Cluster Lifecycle Management (Create, Update, Delete) for PowerVC-based Clusters

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

       

      RHACM: Enable Full Cluster Lifecycle Management (Create, Update, Delete) for PowerVC-based Clusters

       

      2. What is the nature and description of the request?

       

      Currently, Red Hat Advanced Cluster Management (RHACM) can only import and manage pre-existing OpenShift Container Platform (OCP) clusters that are already deployed on IBM Power. The actual provisioning (create) and decommissioning (delete) of these clusters must be handled externally, outside of the RHACM interface.

      This enhancement requests the development of a full provider integration that allows users to natively perform complete cluster lifecycle management tasks, specifically create, update (e.g., scale node pools), and delete, for OCP clusters on PowerVC directly from the RHACM console and API. This would elevate PowerVC to the same level of integration as other cloud providers (like AWS, Azure, GCP, OpenShift-Virtualization and VMware) within RHACM.

       

      3. Why does the customer need this? (List the business requirements here)

       

      •  The customer's primary goal is to provide a CaaS platform for their internal teams. Native RHACM integration is critical to providing a simple, self-service experience for creating and destroying "throw-away" or development/test clusters on demand.
      • The current two-step workflow (create in PowerVC and other tools manually, then import in RHACM) is inefficient and prone to error. With a low two-digit deployment count per month, this operational overhead is significant. A single, integrated workflow managed from one console is required to handle this volume efficiently.
      • Forcing platform consumers to leave the RHACM interface to provision or delete clusters creates a disjointed and cumbersome user experience. This feature is needed to provide a true "single pane of glass" for all cluster management operations on PowerVC.
      • The customer requires a consistent management experience across their hybrid cloud environment. This feature would bring PowerVC to feature parity with other major cloud and virtualization providers already fully supported by RHACM.

       

      4. List any affected packages or components

       

      • Red Hat Advanced Cluster Management (RHACM)
      • OpenShift Cluster API (CAPI)
      • The openshift-install command would likely require modifications to support IPI (Installer-Provisioned Infrastructure) deployments on PowerVC, which RHACM would orchestrate.

              bweidenb@redhat.com Bradd Weidenbenner
              sluetzen Steffen Lützenkirchen
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None