d3a6cdcf99
This patch introduces a new way for configuring which handlers the Kuryr controller should be using. This will allow people to use externally provided handlers as long as they are installed as entrypoints of the right namespace. Implements: blueprint kuryr-pluggable-handlers Change-Id: I52ce0ef00771c8587d7f7113cc5eb4839d1309a5 Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
24 lines
837 B
YAML
24 lines
837 B
YAML
---
|
|
features:
|
|
- |
|
|
Introduced a pluggable interface for the Kuryr controller handlers.
|
|
Each Controller handler associates itself with specific Kubernetes
|
|
object kind and is expected to process the events of the watched
|
|
Kubernetes API endpoints.
|
|
The pluggable handlers framework enable both using externally provided
|
|
handlers in Kuryr Controller and controlling which handlers
|
|
should be active.
|
|
|
|
To control which Kuryr Controller handlers should be active, the selected
|
|
handlers need to be included at the kuryr.conf at the 'kubernetes'
|
|
section.
|
|
If not specified, Kuryr Controller will run the default handlers.
|
|
For example, to enable only the 'vif' controller handler we should set
|
|
the following at kuryr.conf:
|
|
|
|
.. code-block:: ini
|
|
|
|
[kubernetes]
|
|
enabled_handlers=vif
|
|
|