Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-582

Support removal of BYOH instances

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0
    • None
    • wmco
    • None
    • 5
    • False
    • False
    • OCPPLAN-2389 - Drive Workload and Consumption
    • Undefined
    • WinC - Sprint 203

      As an OpenShift cluster administrator I would like to remove an existing Windows instance from the cluster as a worker node.

      Description

      In addition to draining and cordoning nodes corresponding to the entries removed from openshift-windows-machine-config-operator/windows-instances ConfigMap, WMCO should ensure that the instance is removed as a worker from the cluster,

      Engineering details

      On detecting that the list of nodes has IP addresses that do not map to any in the list of instances, WMCO will perform an uninstall operation on the node. This will involve stopping and removing:

      • Monitoring and logging services
      • kube-proxy service
      • hybrid-overlay-node service
      • kubelet service
      • Delete the payload binaries

      Required

      WMCO should only remove BYOH instances that it has added to the cluster.

      Acceptance criteria

      • WMCO should be able to handle draining, cordoning, and removal BYOH instances when their entries are removed from windows-instances.
      • e2e test that exercises the removal of a Windows instance when removed from windows-instances.
      • Update the docs reflecting how to remove a BYOH instance.

              rh-ee-ssoto Sebastian Soto
              paravindh Aravindh Puthiyaparambil (Inactive)
              Shang Gao Shang Gao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: