Topo Kind objects cannot be deleted after sd-ran Helm chart is deleted

[yunowo]

For Topo Kind objects finalizers, onos-operator#29 added a check to see if the namespace is whether being deleted. But when deleting the sd-ran chart, the onos-topo pod is deleted before the Topo Kind finalizers execution, so the Topo Kind objects cannot be deleted. If we want to wait for chart deletion(use kubectl delete), it will be stuck.

Steps to preproduce

1. Install sd-ran helm charts.

kubectl create ns onos-apps
helm install atomix-controller atomix/atomix-controller -n kube-system --version 0.6.8
helm install atomix-raft-storage atomix/atomix-raft-storage -n kube-system --version 0.1.15
helm install onos-operator onos/onos-operator -n kube-system --version 0.5.2
helm install sd-ran sdran/sd-ran -n onos-apps --version 1.4.124

2. check topo kind objects.

root@server-4:/home# kubectl get kinds -n onos-apps
NAME        AGE
contains    36s
controls    36s
e2cell      36s
e2node      36s
e2t         36s
neighbors   36s

3. delete sd-ran helm chart, topo kind objects got deletion timestamps but not deleted.

root@server-4:/home# helm delete sd-ran -n onos-apps
release "sd-ran" uninstalled
root@server-4:/home# kubectl get kinds -n onos-apps
NAME        AGE
contains    81s
controls    81s
e2cell      81s
e2node      81s
e2t         81s
neighbors   81s