Uploaded image for project: 'OpenShift Pod Autoscaling'
  1. OpenShift Pod Autoscaling
  2. PODAUTO-318

Implement HCP karpenter deletion logic

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None

      As an OpenShift HCP management cluster admin, when I delete a HCP cluster with autonode on, I would also want to make sure any provisioned nodes are removed from the infrastructure. We need to make sure Karpenter related objects are not blocking the deletion or would result in resource leakage.

      This story should capture the flow described in https://docs.google.com/document/d/1-dBlqpebNbxBj8Ut2tGDbBzG3Tlbc4BtIizA_6WR0sM/edit?usp=sharing and implements cascading deletion login in the HCP Karpenter operator.

      This should also include e2e test(s) and relevant unit tests which make sure a HCP cluster with autonode on gets successfully deleted.

              rh-ee-macao Max Cao
              rh-ee-macao Max Cao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: