Ingress NGINX Controller for Kubernetes
3032ff166f
Automatic merge from submit-queue Correctly handle ingress.class in GCE controller This bug would only get activated when a user has both `ingess.class=gce` and `ingress.class=nginx` ingresses active in the same GCE/GKE cluster, and would manifest as a set of cloud resources created wastefully for the `ingress.class=nginx` ingress as well. We were previously only ignoring ingress.class (documented here: https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/BETA_LIMITATIONS.md#disabling-glbc) when the ingress was created/deleted/modified. There's a chance another ingress with the correct class results in us entering the `sync` routine and listing all ingresses. The listing routine was not smart enough to ignore `ingress.class=nginx`, so we ended up creating resources for the nginx ingress anyway. The second commit fixes some of the nginx examples to include a `readiness` probe that is == liveness probe. Minhan or Girish, whichever one has spare cycles first. |
||
|---|---|---|
| controllers | ||
| echoheaders | ||
| echoheaders-redirect | ||
| Godeps | ||
| vendor | ||
| OWNERS | ||