When using the registry-overrides flag to override registries for control plane components, it seems like the current implementation propagates the override to some data plane components. 

There was an attempt to resolve this: https://issues.redhat.com/browse/OCPBUGS-32257

but we're still seeing a few components getting the overridden registry propagated to them. The components on the data plane that we noticed still getting their registry values overriden are:

```
konnectivity-agent-*
kube-apiserver-proxy-bpr-*
iptables-alerter-*
```

    100%

    1.Input a registry override through the HyperShift Operator
    2.Check registry fields for all deployments on data plane
    3.

    konnectivity-agent-* kube-apiserver-proxy-bpr-* iptables-alerter-* are getting the overridden registry values propagated to them

    overriden registries should not get propagated to data plane