openstack
/
kuryr-libnetwork
Code Issues Proposed changes

Move the description of the pool member creation 

This patch moves the description of the pool member creation to the
section for the kube-proxy emulation using the LBaaS.

Change-Id: I7e93f31d02cbb518f3910008c1e8513f37dda302
Signed-off-by: Taku Fukushima <f.tac.mac@gmail.com>
This commit is contained in:
Taku Fukushima 2016-06-10 12:58:44 +09:00
parent 9824d94055
commit bdcd788119
No known key found for this signature in database
GPG Key ID: 500E6EE30BCD4368
1 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/devref/k8s_api_watcher_design.rst
View File

@ -75,16 +75,15 @@ API. The apiserver ensures namespaces are created before pods are creted.
Pods contain the information required by creating Neutron ports. If pods are
associated with the specific namespace, the ports are created and associated
with the subnets for the namespace. In this case Raven also creates a LBaaS
member for each port translated from the pod coordinating with the service
translation.
with the subnets for the namespace.
Although it's optional, Raven can emulate kube-proxy_. This is for the network
controller that leverages isolated datapath from ``docker0`` bridge such as
Open vSwitch datapath. Services contain the information for the emulation. Raven
maps kube-proxy to Neutron load balancers with VIPs. For "externalIPs" type K8s
service, Raven associates a floating IP with a load balancer for enabling the
pubilc accesses.
maps kube-proxy to Neutron load balancers with VIPs. In this case Raven also
creates a LBaaS pool member for each port translated from the pod coordinating
with the service translation. For "externalIPs" type K8s service, Raven
associates a floating IP with a load balancer for enabling the pubilc accesses.
================= =============
Kubernetes Neutron