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

Ability to delete worker nodes using GitOps workflow

XMLWordPrintable

    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Delete worker nodes using GitOps / ACM workflow

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

      We use siteConfig to deploy a cluster using the GitOPS / ACM workflow. We can also use siteConfig to add worker nodes to an existing cluster. However, today we cannot delete a worker node using the GitOps / ACM work flow. We need to go and manually delete the resources (BMH, nmstateConfig etc.) and the OpenShift node. We would like to have the node deleted as part of the GitOps workflow.

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

      Worker nodes may need to be replaced for any reason (hardware failures) which may require deletion of a node.

      If we are colocating OpenShift and OpenStack control planes on the same infrastructure (using OpenStack director operator to create OpenStack control plane in OCP virtualization), then we also have the use case of assigning baremetal nodes as OpenShift worker nodes or OpenStack compute nodes. Over time we may need to change the role of those baremetal nodes (from worker to compute or from compute to worker). Having the ability to delete worker nodes via GitOps will make it easier to automate that use case.

      4. List any affected packages or components.

      ACM, GitOps

              bweidenb@redhat.com Bradd Weidenbenner
              abokhari@redhat.com Ali Bokhari
              Votes:
              1 Vote for this issue
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: