title: BackendConfig ignored on Ingress
body: <p>I'm trying to configure GKE ingress to route traffic to IstioIngressgateway.
  in order to do so i do the following:</p>
  <ul>
  <li>Create BackendConfig for customhealthcheck as istio is using 15021 port</li>
  </ul>
  <pre><code>apiVersion: cloud.google.com/v1
  kind: BackendConfig
  metadata:
    name: ingress-backendconfig
    namespace: istio-system
  spec:
    healthCheck:
      requestPath: /healthz/ready
      port: 15021
      type: HTTP
  </code></pre>
  <ul>
  <li>Patch my IstioGateway service to use this backend with:</li>
  </ul>
  <pre><code>kind: Service
  metadata:
    name: istio-ingressgateway
    namespace: istio-system
    annotations:
      cloud.google.com/backend-config: '{&quot;default&quot;: &quot;ingress-backendconfig&quot;}'
      cloud.google.com/neg: '{&quot;ingress&quot;: true}'
  </code></pre>
  <ul>
  <li>Create my ingress using:</li>
  </ul>
  <pre><code>apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    name: istio-ingress
    namespace: istio-system
    annotations:
      kubernetes.io/ingress.global-static-ip-name: main-ingress
      networking.gke.io/managed-certificates: ingress-cert
  spec:
    rules:
    - host: myasm.example.com
      http:
        paths:
        - path: /*
          backend:
            serviceName: istio-ingressgateway
            servicePort: 80
  </code></pre>
  <p>Problem is the Backend for istio created with default healthcheck (serving port 80 and route /), and basically ignores the backend config.</p>
  <p>what can be the reason for that?
  i've tried to delete the resources and recreate them,
  tried also to give the service wrong backend config to see it reads the annotation and he throws event of 'backend config does not exist' so it does read it.</p>
  <p>it might be related to the fact i did it and later re-update the istio installation with istioOperator? is something somewhere hang?
  not sure how can i make it work again.</p>
  <p>as mentioned i've deleted ingress + backendconfig and removed annotation from the service and tried everything all over again, but still the same.</p>
  <p>same approach btw works on another cluster.
  what am i missing and how can i debug it further?</p>
  <p>10x</p>