Allow Deletion of managed resources in Control Plane

[GenosseOtt]

Description

We allow users to create and delete, projects, WS, mcps...

Lets do the same for the resources the control plane holds.

Technical Tasks

• Find out and create API request for resources deletion.
• Add button in proper place and connect it to the API call (In YAML editor/another column in?)
• Deletion confirmation modal
• Refresh view after deletion (?)

Add Button or put behind the three dots to avoid accidental clicks

Deletion Requests

Regular Delete

• DELETE btp/subaccount resource

Force Delete

• DELETE btp/subaccount resource
• PATCH delete resource.metadata.finalizers field

Acceptance Criteria

• Managed Resources (in a ManagedContolPlane) can be deleted via UI [Simple Trash Icon Button next to edit]
• Deletion needs a Deletion Confirmation
• End user can select (default: not selected) "delete finalizers as well" to allow force deletion (warning: may create orphans!)
• Resource can be grayed out, change icon from processing to deletion (meta.deletionTimestamp!)
  https://kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/

Out of scope

• Force Deletion is not possible on Onboarding API (WS, Project, ManagedControlPlane) resources
• Transaction guarantee on deletion

[enrico-kaack-comp]

End user can select (default: not selected) "delete finalizers as well" to allow force deletion (warning: may create orphans!)

I highly suggest to NOT include this functionality. Reasons:

• This is nothing that should be needed in a running system. If an MCP is stuck in deletion, that is an intended state (because the deletion process failed) and requires a support issue. Our DoD can than check what resources failed to delete and clean up manually.
• The mentioned orphans are Gardener Shoot cluster that are also quiet costly. If people really wanna do this they should need as much friction as possible and do it with kubectl.

[GenosseOtt]

I agree 100% with your goal that ideally it should not be needed.

However the state we are at today we experience among customers, and our own setups, that providerconfigs run inactive, or connections to resource providers die for other reasons. As we want to delete idle MCPs, we must go through othem manually, delete finalizers and resources - the underlying orphans are no longer around. Deleting them is pointless.

So why not give this an additional checkmark to run with deletion of finalizer. Its optional, only allowed for Admins - and nothing an end user is prevented from when using the CLI either.

[enrico-kaack-comp]

I missread the issue and thought it is for MCP resource. But we are only talking about Managed Resources, so for that I would be fine and my previous comment does not apply.