anchor.diff:  data from the image registry or Image Registry Operator would be collected from
   `must-gather`. This bug fix ensures the `openshift-image-registry` namespace is
   always included in the Image Registry Operator's related objects. As a result,
  -basic information from the `openshift-image-registry` namespace including pods,
  +basic information from the `openshift-image-registry` namespace including Pods,
   deployments, and services is always collected by `must-gather`.
   (link:https://bugzilla.redhat.com/show_bug.cgi?id=1748436[*BZ#1748436*])
   
  
positive.code: the old `network-attachment-definition`. You must delete the resources manually.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1755586[*BZ#1755586*])
  
  * The SRIVO Operator pod crashes when NAD is manually created.
  (link:https://bugzilla.redhat.com/show_bug.cgi?id=1755188[*BZ#1755188*])
  
  * No proxy is set for `kube-controller-manager`.
  
negative.code: and xref:../operators/olm-restricted-networks.adoc#olm-restricted-networks[Using Operator Lifecycle Manager on restricted networks]
  for details.
  
  [id="ocp-4-2-three-node-bare-metal-deployments"]
  ==== Three-node bare metal deployments (Technology Preview)
  In {product-title} {product-version}, the ability to deploy a cluster without distinct compute, or worker nodes, on bare metal clusters is a Technology Preview feature. If you do not create worker machines when you install your cluster on bare metal infrastructure that you provision, all Pods, including the router Pods, are deployed on the control plane, or master, machines instead. Note that this deployment method is not available in cloud-based clusters in {product-title} {product-version}. It is not recommended to use technology preview features in production clusters.
  
  [id="ocp-4-2-cluster-wide-egresss-proxy"]
  ==== Cluster-wide egress proxy
  
  