Projects stuck on deletion shows misleading message

[dnaeon]

What happened:

Deleting a project got stuck and the dashboard was suggesting that it deletion is still pending because of existing backupentries.

However, checking the project namespace shows that there are no backupentries.

> kubectl --namespace garden-myproject get backupentries
No resources found in garden-myproject namespace.

What appears to be blocking the project namespace deletion in this particular case are secrets with attached finalizers. There might be other resources, though.

The message however displayed on the dashboard is misleading and might confuse people when trying to understand why deletion is stuck.

What you expected to happen:

Better message indicating the reason why deletion is stuck.

How to reproduce it (as minimally and precisely as possible):

• Create a new project.
• Create a new secret and add a finalizer to it
• Delete the project

Anything else we need to know:

Environment:

[petersutter]

We could check the deletionTimestamp if it is older than e.g. 1w, to determine if the deletion is stuck. If so, display a different, generic message than the regular project deletion hint text.

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages 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
• Mark this issue as rotten with /lifecycle rotten
• Close this issue with /close

/lifecycle stale