diff options
| author | Quinton Hoole <quinton@google.com> | 2016-11-11 14:21:06 -0800 |
|---|---|---|
| committer | Quinton Hoole <quinton@google.com> | 2016-11-11 14:21:06 -0800 |
| commit | a9c78c0490aff3ecf9a5cb7c02662675f9ce903e (patch) | |
| tree | 6194f298386b47d3ec69d9c09afa724ac9a35e2f | |
| parent | 8ed294b220fed0146ac32cce499f107d0f450ee9 (diff) | |
Address review comments.
| -rw-r--r-- | federated-ingress.md | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/federated-ingress.md b/federated-ingress.md index c0ab3381..05d36e1d 100644 --- a/federated-ingress.md +++ b/federated-ingress.md @@ -92,9 +92,16 @@ In summary, all of [GCE L7 Load Balancer](https://cloud.google.com/compute/docs/ ### Implementation -1. Federation user creates (federated) Ingress object -1. Federated Ingress Controller creates Ingress object in each cluster in the federation -1. Each cluster-level Ingress Controller ("GLBC") creates Google L7 Load Balancer machinery (forwarding rules, target proxy, URL map, backend service, health check) which ensures that traffic to the Ingress (backed by a Service), is directed to one of the nodes in the cluster. +1. Federation user creates (federated) Ingress object (the services + backing the ingress object must share the same nodePort, as they + share a single GCP health check). +1. Federated Ingress Controller creates Ingress object in each cluster + in the federation (after [configuring each cluster ingress + controller to share the same ingress UID](https://gist.github.com/bprashanth/52648b2a0b6a5b637f843e7efb2abc97)). +1. Each cluster-level Ingress Controller ("GLBC") creates Google L7 + Load Balancer machinery (forwarding rules, target proxy, URL map, + backend service, health check) which ensures that traffic to the + Ingress (backed by a Service), is directed to the nodes in the cluster. 1. KubeProxy redirects to one of the backend Pods (currently round-robin, per KubeProxy instance) An alternative implementation approach involves lifting the current |