Value Statement

In hypershift use case, the hypershift hosting(management) clusters are created by OCM hive. currently, if we destroy a hosting cluster that is hosting some other hyeprshift hosted cluster, the control plane of these hosted clusters would also be destroyed, but the infrastructure of these hosted clusters would remain. Add a webhook to validate clusterDeployment deletion of hosting clusters can prevent it from happening.

Definition of Done for Engineering Story Owner (Checklist)

When the hypershift addon is available on the hosting cluster：

• [x] Managed cluster of the hosting cluster can not be deleted if it is hosting a hypershift hosted control plane
• [x] Cluster deployment of the hosting cluster can not be deleted before it is detached from the hub

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [x] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [x] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [-] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [-] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [x] The must-gather script has been updated.