Install Skupper controller in both Cluster scope and Namespace scope at the same time causes conflicts

[granzoto]

Installing the Skupper V2 using helm chart in both Cluster scope and Namespace scope, in the same cluster, causes conflicts in the namespace where the controller is installed as namespace level.
Using a single site config in the namespace, it deploys the router as expected, but then from time to time a second router starts, but dies in init mode.

Install the Skupper helm chart in cluster scope.
Create a namespace and install the Skupper helm chart in namespace scope
Create a single skupper site in the namespace
Monitor the pods in the namespace. You will see a second router instance been created, but it never gets up, it dies in init status.

The second instance of the router should not be created

• Version : Skupper V2 helm chart
• Platform: Openshift 4.17 and 4.16

NAME READY STATUS RESTARTS AGE
iperf3-server-b-596ccf9b6f-qr8p8 1/1 Running 0 17d
skupper-controller-7697b4c78f-qwpbk 1/1 Running 0 17d
skupper-router-776c445d6c-gswp2 2/2 Running 0 10m
skupper-router-c5ff7ffdb-tnwxw 0/2 Init:0/1 0 1s

[grs]

See #1926 for solution to this problem.