<--- Ability to destroy a managed cluster which was not created using ACM --->

Epic Goal

Destroy option for non ACM provisioned managed clusters.

Why is this important?

• ACM will detach the registered GCP OCP IPI cluster and destroy the GCP cloud resources associated with the GCP OCP IPI Cluster, such as worker/master VMs, FW rules, Static IPs, LB, HC, DNS zone with records, Service Accounts etc.
• We need a way that we can not only register the OCP IPI cluster from the public cloud to the ACM but also import terraform and cluster states when the OCP IPI clusters are created outside of ACM.

  Scenarios

Step 1. Manually create an OCP IPI cluster on GCP with openshift-install.
Step 2. Register the newly created OCP IPI cluster from GCP to the ACM cluster.
Step 3. Try to destroy the newly registered GCP OCP IPI cluster from the ACM console.

Acceptance Criteria

Should be able to destroy managed cluster from ACM UI which are not provisioned through ACM.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. Migrated from the bugzilla : https://bugzilla.redhat.com/show_bug.cgi?id=2152528

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>