parent
72c78a9788
commit
bc5951ca10
|
@ -293,7 +293,7 @@ Check that:
|
|||
[the GLBC docs](https://github.com/kubernetes/ingress/blob/7dcb4ae17d5def23d3e9c878f3146ac6df61b09d/controllers/gce/README.md)
|
||||
for further information. To remedy this,
|
||||
delete any ingresses created before the cluster joined the
|
||||
federation (and had it's GLBC reconfigured), and recreate them if
|
||||
federation (and had its GLBC reconfigured), and recreate them if
|
||||
necessary.
|
||||
{% endcapture %}
|
||||
|
||||
|
|
|
@ -311,7 +311,7 @@ protocol between the loadbalancer and backend to communicate the true client IP
|
|||
such as the HTTP [X-FORWARDED-FOR](https://en.wikipedia.org/wiki/X-Forwarded-For)
|
||||
header, or the [proxy protocol](http://www.haproxy.org/download/1.5/doc/proxy-protocol.txt).
|
||||
Loadbalancers in the second category can leverage the feature described above
|
||||
by simply creating a HTTP health check pointing at the port stored in
|
||||
by simply creating an HTTP health check pointing at the port stored in
|
||||
the `service.spec.healthCheckNodePort` field on the Service.
|
||||
|
||||
{% endcapture %}
|
||||
|
|
Loading…
Reference in New Issue