In a HyperShift management cluster, the cluster's
 CNO should only manage the networking components that belong to the 
management cluster. CNO's running as pods in hosted control plane 
namespaces own the management of the networking components for their 
respective hosted clusters.

Based on the logs of the CNO of a management cluster, it seems that 
the operator is incorrectly attempting to reconcile the ovnkube-master 
deployment inside a hosted cluster control plane namespace:


network-operator-c65867784-s6ph9 network-operator I0828 
14:30:50.541952       1 pod_watcher.go:124] Operand /, Kind= 
ocm-jdzon-1u9o7iloec6vgbieph3jsrh77hmc41ns-jdzon-1/ovnkube-master 
updated, re-generating status
            

4.12

Always

                    
1. Install hypershift running on a cluster using OVNKubernetes as its SDN.

2. Create a HostedCluster on that management cluster.

3. Observe the logs of the CNO of the management cluster.
                 

Management clusters CNO reconciles status based on resources deployed in the hosted cluster

Management clusters CNO reconciles status only from management clusters resources