openstack/kuryr-kubernetes
Code Issues Proposed changes

Merge "Update the Handlers and the Resources"

Browse Source
This commit is contained in:
Zuul 2021-06-22 07:20:14 +00:00 committed by Gerrit Code Review
commit 5d2ac1c691
1 changed files with 22 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/source/devref/kuryr_kubernetes_design.rst
View File

@ -88,7 +88,11 @@ Watcher is a common software component used by both the Controller and the CNI
driver. Watcher connects to Kubernetes API. Watcher's responsibility is to
observe the registered (either on startup or dynamically during its runtime)
endpoints and invoke registered callback handler (pipeline) to pass all events
from registered endpoints.
from registered endpoints. As an example, if a Service is created at the
Kubernetes end, the ServiceHandler which is watching the Service Objects uses
the watcher to detect the changes on them and calls the right driver for the
reconciliation of Kubernetes and the needed OpenStack resources.
Event Handler
@ -173,15 +177,23 @@ handlers need to be included in kuryr.conf at the 'kubernetes' section.
If not specified, Kuryr Controller will run the default handlers, which
currently includes the following:
================== =========================
====================== =========================
Handler Kubernetes resource
================== =========================
====================== =========================
vif Pod
kuryrport KuryrPort CRD
endpoints Endpoints
service Service
kuryrloadbalancer KuryrLoadBalancer CRD
================== =========================
kuryrnetwork KuryrNetwork CRD
namespace Namespaces
kuryrnetworkpolicy KuryrNetworkPolicy CRD
podlabel Pod
policy NetworkPolicy
machine Machine
kuryrnetworkpopulation KuryrNetwork CRD
====================== =========================
For example, to enable only the 'vif' controller handler we should set the
following at kuryr.conf: