Can not delete k8s cluster when OpenStack’s soft delete feature is enabled

[HowardXi]

/kind bug

What steps did you take and what happened:
When OpenStack’s soft delete feature is enabled, the delete method called by CAPO (Cluster API Provider OpenStack) cannot fully remove the virtual machines and their associated resources.
As a result, the Kubernetes cluster deletion process gets stuck at a certain step because the instances remain in a “soft deleted” state instead of being completely removed.

[HowardXi]

This issue still persists in the latest version (0.12.4) because CAPO calls the standard servers.Delete method instead of the servers.ForceDelete method.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale