github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix.

Browse Source
This commit is contained in:
Eric Tune 2015-01-21 13:28:35 -08:00
parent 845f0e9dd1
commit cb6d23b186
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/availability.md
View File

@ -126,7 +126,7 @@ calls for maximum 100 node clusters at v1.0 and maximum 1000 node clusters in th
## Working with multiple clusters ## Working with multiple clusters
When you have multiple clusters, you would typically copies of a given service in each cluster and put each of those When you have multiple clusters, you would typically create services with the same config in each cluster and put each of those
service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer), so that service instances behind a load balancer (AWS Elastic Load Balancer, GCE Forwarding Rule or HTTP Load Balancer), so that
failures of a single cluster are not visible to end users. failures of a single cluster are not visible to end users.