User Story:

As a (user persona), I want the installer to configure the default router to use dual-stack Network Load Balancer (NLB).

Currently, NLB does not support single-stack IPv6 and classic LB supports only IPv4. 

Acceptance Criteria:

Description of criteria:

• Ingress manifest provided to the Ingress Controller Operator should specify type as NLB and IP-type as dual-stack.

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• Code that generates ingress manifest for the Ingress Controller Operator: https://github.com/openshift/installer/blob/fe225d16eef71880ba4cd8027f6f9e5b2b0d3063/pkg/asset/manifests/ingress.go 
• As of now, the cluster ingress operator does not support configuring the NLB as dual-stack. The support is also blocked by AWS CCM not supporting dual-stack NLB.
• Possible workaround:
  • Configure to publish the ingress controller via NodePort service.
  • Manually (i.e. installer), create the dualstack NLB, and registery the nodes.
  • Essentially, it is the same setup as when the ingress operator would (in the future) manage. Just that, at this point, the load balancer mangement is offloaded to us (installer).
  • Reference: https://github.com/openshift/cluster-ingress-operator?tab=readme-ov-file#nodeportservice 

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