openstack
/
kuryr-kubernetes
Code Issues Proposed changes

Added the Service Creation Flow Diagram 

Change-Id: Idc4b724c6fbfe3eba660da521eea761667d04ac1
This commit is contained in:
Sunday Mgbogu 2021-06-25 10:35:58 +01:00
parent aae39f5011
commit 512d6d80e0
4 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/images/service_creation_diagram.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

1
doc/images/service_creation_diagram.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 304 KiB

BIN
doc/images/service_creation_flow.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 47 KiB

17
doc/source/devref/service_support.rst
View File

@ -107,7 +107,22 @@ Endpoints information is not yet added on the spec by the EndpointHandler, the
event reaching KuryrLoadBalancerHandler is skipped. If the EndpointsHandler
starts handling the on_present event first, the KuryrLoadBalancer CRD is
created with the endpoints subsets. Otherwise, it will update the existing CRD
created by the ServiceHandler with the endpoints subsets.
created by the ServiceHandler with the endpoints subsets. Please see below the
the service creation flow diagram:
.. image:: ../../images/service_creation_flow.png
:alt: Service creation flow
:align: center
:width: 100%
Also, find below how the handlers and drivers handle service creation:
.. image:: ../../images/service_creation_flow.png
:alt: Service creation flow
:align: center
:width: 100%
The KuryrLoadBalancerHandler (at controller/handlers/loadbalancer.py) upon
noticing the KuryrLoadBalancer CRD with the full specification, calls the