openstack/kuryr-kubernetes
Code Issues Proposed changes

Update service documentation with Octavia loadbalancer topology configurtaion.

Browse Source 
When octavia is configured to SINGLE loadbalancer topology, we have a single point of failure
(Amphora), that's affect both user services and kuryr-kuberenets L7 router module.

Service documentation is updated with that info.

Change-Id: I04e2deaf155a43c26d9f008a03b13c05c5286a48
Closes-Bug: #1737978
This commit is contained in:
Yossi Boaron 2017-12-13 16:27:09 +02:00
parent c468b28c38
commit d76558b303
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/source/installation/services.rst
View File

@ -85,9 +85,12 @@ network namespace is used by Octavia to reconfigure and monitor the Load
Balancer, which it talks to via HAProxy's control unix domain socket.
Running Kuryr with Octavia means that each Kubernetes service that runs in the
cluster will need one Load Balancer VM, i.e., an *Amphora*. It is important to
configure the right Octavia flavor for your deployment and to size the compute
nodes appropriately so that Octavia can operate well.
cluster will need at least one Load Balancer VM, i.e., an *Amphora*.
To avoid single point of failure at Amphora, Octavia should be configured to
support active/standby loadbalancer topology.
In addition, it is important to configure the right Octavia flavor for your
deployment and to size the compute nodes appropriately so that Octavia can
operate well.
Another important consideration is where do the Amphorae run, i.e., whether the
worker nodes should also be compute nodes so that they run the Amphorae or if