Goal of the card,

1. We have a set of metrics/alerts/telemetry that are exposed - some for the control-plane and some for the data-plane mkennell@redhat.com has this great doc with the whole list if the CNO/OVNK files don't give enough info on the OVN related metrics. Go through them figure out which ones need changes example some of the master components are going to the node like northd/sbdb/nbdb - will this entail any changes we need to do?
2. The new set of pods look like this:

```

ovn-kubernetes       ovnkube-cluster-manager-66f9579b6-h8kj2     1/1     Running   0              5m24s   172.19.0.4   ovn-control-plane   <none>           <none>
ovn-kubernetes       ovnkube-local-49w69                         7/7     Running   2 (5m3s ago)   5m24s   172.19.0.4   ovn-control-plane   <none>           <none>
ovn-kubernetes       ovnkube-local-b8rnm                         7/7     Running   2 (5m3s ago)   5m24s   172.19.0.3   ovn-worker2         <none>           <none>
ovn-kubernetes       ovnkube-local-hd7zs                         7/7     Running   2 (5m3s ago)   5m24s   172.19.0.2   ovn-worker          <none>           <none>

```

As you can see there is NO ovnkube-master pod We deff need to change existing metrics around this. ovnkube-local-master is going to be inside the ovnkube-local pod.