Questions about deleting private Namespace

[klboke]

• As the diagram suggests, when the user deletes the private namespace, the interface is not the same as when the administrator deletes it, and it does not look like it is actually deleted
• Many users are confused when deleting, why am I authorized to delete Namespace, and then prompted to fill in the missing Namespace
• Would it be better to keep the user deletion logic consistent with the administrator deletion logic here?

[nobodyiam]

Would it be better to keep the user deletion logic consistent with the administrator deletion logic here?

I think we could modify the logic to make it consistent with the administrator deletion logic. But we may add some tips so that the user know what the impact is, e.g. the private namespace in all envs and clusters are deleted, not just the current one.

[klboke]

Public Namespace deletion also has the same problem

• For example, if a user deletes the Public Namespace of 'Test.kl' and then creates a Private Namespace with the same name, it will report that a Namespace with the same name already exists.

• Of course, continuing to create a Public Namespace with the same name ('Test.kl') will also fail due to the existence of an AppNamespace

• From the user's point of view, this is also not logically expected.

[klboke]

PR：#4499