-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
2
-
None
-
Installer Sprint 268, Installer Sprint 269
User Story:
The installer will apply the specified IngressControllerLB subnets to the default IngressController's spec.endpointPublishingStrategy.loadBalancer.providerParameters.aws.classicLoadBalancer.subnets or ...networkLoadBalancer.subnets field (based on platform.aws.lbType) in the manifest generated by the generateDefaultIngressController function.
Acceptance Criteria:
Description of criteria:
- Ingress LB is placed on specific subnet(s) as specified by user
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- For sanity checking, you can run openshift-install create manifests and check the cluster-ingress-*.yaml manifests
- https://github.com/openshift/installer/blob/main/pkg/asset/manifests/ingress.go
- If no roles are specified in the installconfig, no subnets are supplied in the manifest
This requires/does not require a design proposal.
This requires/does not require a feature gate.