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

Simplify day-2 master node replacement operation

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • openshift-4.17
    • Node
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Simplify day-2 master node replacement operation

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

      One of the key day-2 operation is to perform master node replacement (in case of any issue with the master nodes). As of now the method to perform day-2 master node replacement varies based on the type of installation (IPI/UPI/AI/ABI).

      One such use case:

      A customer having RHOCP cluster installed using ABI installed method on physical servers having no access to their BMC. As of now the official master node [replacement document](https://docs.openshift.com/container-platform/4.17/backup_and_restore/control_plane_backup_and_restore/replacing-unhealthy-etcd-member.html#restore-replace-stopped-baremetal-etcd-member_replacing-unhealthy-etcd-member) states, BMC access is required to perform master node replacement.

      It would be helpful to have a feature similar to OCPSTRAT-784 which enables simplified process of adding compute node across format.

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

      A customer having RHOCP cluster installed using ABI installed method on physical servers having no access to their BMC.

      4. List any affected packages or components.

      agent service

              racedoro@redhat.com Ramon Acedo
              rhn-support-chdeshpa Chinmay Deshpande
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: