Ingress pod stops applying ingress objects once it runs into one that it rejects

[cweidinger]

Describe the bug
When Ingress pod finds an ingress object it rejects, it just stops updating ingress proxy config. It should skip over ingress objects it doesn't agree with and keep applying other ingresses.

To Reproduce
0. be using gloo as ingress controller

1. apply ingress that has servicePort: servicePortName which the ingress pod currently rejects and then an ingress that it shouldn't reject.
   apiVersion: extensions/v1beta1
   kind: Ingress
   metadata:
   name: hc-ingress1
   namespace: default
   spec:
   rules:

• host: myhost1
  http:
  paths:
  • backend:
    serviceName: myservicename
    servicePort: myserviceportname

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: hc-ingress2
namespace: default
spec:
rules:

• host: myhost2
  http:
  paths:
  • backend:
    serviceName: myservicename
    servicePort: 8080

3. see that neither ingress was applied to the proxies object
   $ k get proxies -o yaml ingress-proxy -n gloo-admin
4. See rejection in logs
   $ k logs ingress-6564685644-n6d5k -n gloo-admin | grep rejected
5. Fix and apply ingress objects
6. see everything works

Expected behavior
Even if hc-ingress1 fails hc-ingress2 should work but it currently doesn't until hc-ingress1 is fixed. If 1 app team deploys a broken ingress, it shouldn't prevent other app teams from deploying their ingress changes.

Additional context

• Gloo version 1.3.27
• Kubernetes version 1.14