-
Feature Request
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
As a customer I want to switch an OCP Ingress from a AWS Classic Load Balancer to AWS Network Load Balancer. I should be able to do this without having to delete and recreate the IngressController object.
Today changing the ELB from Classic to Network requires deleting the IngressController object and recreating it with the correct ProviderParameters.
Its understood that this process would cause ingress interruption as does switching the endpointPublishingStrategy scope. A recent feature introduced the ability to switch endpointPublishingStrategy and acknowledging the ingress interruption with an annotation, this same workflow could be suitable for switching ELB types. See https://issues.redhat.com/browse/NE-621
Another related RFE asks to ensure deleted IngressController objects are recreated as the correct ELB type see https://issues.redhat.com/browse/NE-799. Today if you delete this object after an NLB has been specified it will return with out the ProviderParameters specified and as a classic load balancer.
- relates to
-
NE-799 Allow NLB to be configured as default load balancer option for IngressController objects
-
- Closed
-