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.

[maweibin]

你好，这个删除namespace的动作在新版本2.4.0版本的时候，和以前完全不一样，现在在某个集群下的namespace删除，会直接删除所有环境下的namespace，但是删除按钮却在当前集群，会给人一种错觉，认为我只是删除当前集群下的namesapce，导致从1.x版本升级到2.4.0的时候，很多用户误删除了其他集群里面正在使用的namespace，或者这个集群下的namespace还是删除当前的集群下的namepsace，应用下的删除namespace是不是放在其他其他

[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