From 75531c6315cf1165247b7b98e374cb63518dfb02 Mon Sep 17 00:00:00 2001 From: bprashanth Date: Mon, 19 Sep 2016 11:19:58 -0700 Subject: [PATCH] Clarify Ingress multizone docs. --- docs/user-guide/ingress.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/user-guide/ingress.md b/docs/user-guide/ingress.md index 1c82fb3676cea..6ce1eb915d10a 100644 --- a/docs/user-guide/ingress.md +++ b/docs/user-guide/ingress.md @@ -271,6 +271,10 @@ test - 178.91.123.132 You can achieve the same by invoking `kubectl replace -f` on a modified Ingress yaml file. +## Failing across availability zones + +Techniques for spreading traffic across failure domains differs between cloud providers. Please check the documentation of the relevant Ingress controller for details. Please refer to the federation [doc](/docs/user-guide/federation/) for details on deploying Ingress in a federated cluster. + ## Future Work * Various modes of HTTPS/TLS support (eg: SNI, re-encryption)