httpsRedirect doesnt seem to work with user created ingress gateway

Networking
1

Hello,

I’m running Istio 1.4.2 on EKS 1.14 with the following configuration.

As you can see I’ve disabled default ingress-gateway and create a few with a helm loop, each of which serves on a different domain.

Now, all the gateways attached to these ingress gateways are not honouring the httpsRedirect flag for a Gateway.

Given I have a test cluster, I decided to try with the same Gateway configuration but on the default ingress gateway and it just works.

Is there any additional configuration I have to make in order to make httpsRedirect to work on a user defined ingress gateway?

Thanks

      values: |
        gateways:
          enabled: true

          istio-ingressgateway:
            enabled: false

          {{ range $lb  := $.Values.istioIngressgateways -}}
          {{ $lb.name }}:
            enabled: true
            labels:
              app: istio-ingressgateway
              istio: ingressgateway
              tld: {{ $lb.tld }}
            serviceAnnotations:
              service.beta.kubernetes.io/aws-load-balancer-ssl-cert: {{ $lb.sslCertificate | quote }}
              service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: "false"
              service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: "60"
              service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
              service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
            type: LoadBalancer
            ports:
              ## You can add custom gateway ports
            - port: 80
              targetPort: 80
              name: http2
              nodePort: {{ $lb.http2 }}
            - port: 443
              name: https
              nodePort: {{ $lb.https }}
            autoscaleEnabled: true
            autoscaleMin: {{ $lb.replicaCount }}
            autoscaleMax: 5
            rollingMaxSurge: 100%
            rollingMaxUnavailable: 25%
            resources:
              requests:
                cpu: 100m
                memory: 128Mi
              limits:
                cpu: 2000m
                memory: 1024Mi
            cpu:
              targetAverageUtilization: 80

          {{ end }}
2

Eventually found out someone added

---
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: {{ $fullName }}
spec:
  workloadLabels:
    istio: ingressgateway
  filters:
    - filterName: envoy.lua
      filterType: HTTP
      filterConfig:
        inlineCode: |
          function envoy_on_request(request_handle)
            request_handle:headers():replace("x-forwarded-proto", "https")
          end
          function envoy_on_response(response_handle)
          end

Once deleted it, it started working again.