-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.15, 4.16, 4.17, 4.18
-
Important
-
No
-
NE Sprint 261
-
1
-
Rejected
-
False
-
Description of problem:
IngressControllers created without specifying a spec.endpointPublishingStrategy.loadBalancer.providerParameters.aws.type should use the default specified in the ingresses.config.openshift.io.spec.loadBalancer.platform.aws.type. When this default is NLB, and an IngressController is created without specifying LB Type, but spec.endpointPublishingStrategy.loadBalancer.providerParameters is NOT empty, the defaulting doesn't work (instead uses the universal default of Classic). But when providerParameters is empty, default works correctly.
Version-Release number of selected component (if applicable):
TBD (Need more testing, most likely more version affected)
How reproducible:
100%
Steps to Reproduce:
1. oc edit ingresses.config.openshift.io cluster 2. Set spec.loadBalancer.platform.aws.type to NLB 3. Create IngressController with providerParameters non-empty, but with no LB Type: oc apply -f - <<EOF apiVersion: operator.openshift.io/v1 kind: IngressController metadata: name: nlb namespace: openshift-ingress-operator spec: domain: $domain replicas: 1 endpointPublishingStrategy: loadBalancer: scope: External dnsManagementPolicy: Managed providerParameters: type: AWS type: LoadBalancerService nodePlacement: nodeSelector: matchLabels: node-role.kubernetes.io/worker: "" EOF
Actual results:
IngressController load balancer will use Classic
Expected results:
IngressController load balancer should use NLB
Additional info:
- is caused by
-
NE-975 Ingress controller logic to handle automatic recreation of AWS LB as per installation.
- Closed
- links to