Cluster Network Operator managed component multus-admission-controller does not conform to Hypershift control plane expectations.

When CNO is managed by Hypershift, multus-admission-controller and other CNO-managed deployments should run with non-root security context. If Hypershift runs control plane on kubernetes (as opposed to Openshift) management cluster, it adds pod security context to its managed deployments, including CNO, with runAsUser element inside. In such a case CNO should do the same, set security context for its managed deployments, like multus-admission-controller, to meet Hypershift security rules.

Always

1.Create OCP cluster using Hypershift using Kube management cluster
2.Check pod security context of multus-admission-controller

no pod security context is set on multus-admission-controller

pod security context is set with runAsUser: xxxx

Corresponding CNO change