openstack/kuryr-kubernetes
Code Issues Proposed changes

Merge "Update service documentation with Octavia loadbalancer topology configurtaion."

Browse Source
This commit is contained in:
Zuul 2017-12-28 05:51:23 +00:00 committed by Gerrit Code Review
commit acd3a9c865
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. 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 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 cluster will need at least one Load Balancer VM, i.e., an *Amphora*.
configure the right Octavia flavor for your deployment and to size the compute To avoid single point of failure at Amphora, Octavia should be configured to
nodes appropriately so that Octavia can operate well. 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 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 worker nodes should also be compute nodes so that they run the Amphorae or if