User Story:

kube-controller-manager expects the dualstack cluster(pod) and service CIDRs to be passed as comma-separated list argument [0].

However, the cluster-kube-controller-manager-operator (CKCMO) set separate kube-controller-manager argument for each CIDR family [1][2]. This results in only the one CIDR family (i.e. whichever specified last in the CIDR list) to be set.

Acceptance Criteria:

Description of criteria:

• Dualstack cluster and service CIDRs should be passed to kube-controller-manager as comma-separated list arguments.

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• [0] https://kubernetes.io/docs/concepts/services-networking/dual-stack/#configure-ipv4-ipv6-dual-stack 
• [1] https://github.com/openshift/cluster-kube-controller-manager-operator/blob/3b20c534b1b92d46055147c4f82f69b2ad3044c9/bindata/bootkube/config/bootstrap-config-overrides.yaml#L17-L23
• [2] https://github.com/openshift/cluster-kube-controller-manager-operator/blob/ffe5113eb88f384981fdeff599f22599e11a9d7c/pkg/operator/targetconfigcontroller/targetconfigcontroller.go#L678-L682 

This requires/does not require a design proposal.
This requires/does not require a feature gate.