I’m running an Istio 1.7.6 installation ( with istio-operator ) and recently there was the need to provision a custom ingress gateway, balanced by a NLB in AWS. I added a new “IngressGateways” block in my IstioOperator CR which did work fine - a new NLB was provisioned in AWS.
The issue is: if I need to add a new port ( which in fact means a new listener in NLB ) , there is downtime in every listeners already configured there, so if I have this in my IstioOperator:
service: ports: - name: status-port port: 15021 targetPort: 15021 - name: tcp port: 9000
and decide to add a port 9001:
service: ports: - name: status-port port: 15021 targetPort: 15021 - name: tcp port: 9000 - name: tcp-testing port: 9001
The listener in port 9000 will be affected when adding any other listener. Directly in AWS console, I can verify that every listener is registering a new target group at this time and that’s why I have downtime but it does not make sense why a new target group registration is triggered since there was no changes in that listener - in fact, If I edit my “kind: Service” and add manually a new port, a new listener will appear in NLB without affecting any other listeners.