Browse Source

corrects Kubernetes Services handlers

The handlers that need to be enabled to correctly handle
Kubernetes Services events are (endpoints,service,kuryrloadbalancer)
and not (lb,lbaasspec) as placed in most of the docs.
This was due to the recent movement to KuryrLoadBalancer custom
resources definitions (CRD).

Change-Id: I0eff3b68839a659d39650e2cb22956e30d2c7332
Closes-Bug: #1899013
changes/09/757609/7
Kafilat Adeleke 6 months ago
parent
commit
2f828486c7
9 changed files with 25 additions and 17 deletions
  1. +1
    -1
      devstack/local.conf.odl.sample
  2. +1
    -2
      devstack/local.conf.openshift.sample
  3. +1
    -2
      devstack/local.conf.ovn.sample
  4. +1
    -1
      devstack/local.conf.sample
  5. +2
    -2
      doc/source/devref/kuryr_kubernetes_design.rst
  6. +6
    -3
      doc/source/installation/network_namespace.rst
  7. +7
    -3
      doc/source/installation/network_policy.rst
  8. +4
    -2
      doc/source/installation/ports-pool.rst
  9. +2
    -1
      kuryr_kubernetes/config.py

+ 1
- 1
devstack/local.conf.odl.sample View File

@ -160,7 +160,7 @@ enable_service kuryr-daemon
# By default, some Kuryr Handlers are set for DevStack installation. This can be
# further tweaked in order to enable additional ones such as Network Policy. If
# you want to add additional handlers those can be set here:
# KURYR_ENABLED_HANDLERS = vif,lb,lbaasspec
# KURYR_ENABLED_HANDLERS = vif,endpoints,service,kuryrloadbalancer,kuryrport
# Kuryr Ports Pools
# =================


+ 1
- 2
devstack/local.conf.openshift.sample View File

@ -158,8 +158,7 @@ enable_service kuryr-daemon
# By default, some Kuryr Handlers are set for DevStack installation. This can be
# further tweaked in order to enable additional ones such as Network Policy. If
# you want to add additional handlers those can be set here:
# KURYR_ENABLED_HANDLERS = vif,lb,lbaasspec
# KURYR_ENABLED_HANDLERS = vif,endpoints,service,kuryrloadbalancer,kuryrport
# Kuryr Ports Pools
# =================
#


+ 1
- 2
devstack/local.conf.ovn.sample View File

@ -208,8 +208,7 @@ KURYR_K8S_CONTAINERIZED_DEPLOYMENT=True
# By default, some Kuryr Handlers are set for DevStack installation. This can be
# further tweaked in order to enable additional ones such as Network Policy. If
# you want to add additional handlers those can be set here:
# KURYR_ENABLED_HANDLERS = vif,lb,lbaasspec
# KURYR_ENABLED_HANDLERS = vif,endpoints,service,kuryrloadbalancer,kuryrport
# Kuryr Ports Pools
# =================
#


+ 1
- 1
devstack/local.conf.sample View File

@ -188,7 +188,7 @@ enable_service kuryr-daemon
# By default, some Kuryr Handlers are set for DevStack installation. This can be
# further tweaked in order to enable additional ones such as Network Policy. If
# you want to add additional handlers those can be set here:
# KURYR_ENABLED_HANDLERS = vif,lb,lbaasspec
# KURYR_ENABLED_HANDLERS = vif,endpoints,service,kuryrloadbalancer,kuryrport
# Kuryr Ports Pools
# =================


+ 2
- 2
doc/source/devref/kuryr_kubernetes_design.rst View File

@ -178,8 +178,8 @@ currently includes the following:
================ =========================
vif Pod
kuryrport KuryrPort CRD
lb Endpoint
lbaasspec Service
endpoints Endpoint
service Service
================ =========================
For example, to enable only the 'vif' controller handler we should set the


+ 6
- 3
doc/source/installation/network_namespace.rst View File

@ -13,7 +13,8 @@ the next steps are needed:
.. code-block:: ini
[kubernetes]
enabled_handlers=vif,lb,lbaasspec,namespace,kuryrnetwork,kuryrport
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,namespace,
kuryrnetwork,kuryrport
Note that if you also want to enable prepopulation of ports pools upon new
namespace creation, you need to also add the kuryrnetwork_population
@ -22,7 +23,8 @@ the next steps are needed:
.. code-block:: ini
[kubernetes]
enabled_handlers=vif,lb,lbaasspec,namespace,kuryrnetwork,kuryrport,kuryrnetwork_population
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,namespace,
kuryrnetwork,kuryrport,kuryrnetwork_population
#. Enable the namespace subnet driver by modifying the default
pod_subnet_driver option at kuryr.conf:
@ -73,7 +75,8 @@ to add the namespace handler and state the namespace subnet driver with:
.. code-block:: console
KURYR_SUBNET_DRIVER=namespace
KURYR_ENABLED_HANDLERS=vif,lb,lbaasspec,namespace,kuryrnetwork,kuryrport
KURYR_ENABLED_HANDLERS=vif,endpoints,service,kuryrloadbalancer,namespace,
kuryrnetwork,kuryrport
.. note::


+ 7
- 3
doc/source/installation/network_policy.rst View File

@ -10,7 +10,9 @@ be found at :doc:`./devstack/containerized`):
.. code-block:: ini
[kubernetes]
enabled_handlers=vif,lb,lbaasspec,policy,pod_label,namespace,kuryrnetwork,kuryrnetworkpolicy,kuryrport
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,policy,
pod_label,namespace,kuryrnetwork,kuryrnetworkpolicy,
kuryrport
Note that if you also want to enable prepopulation of ports pools upon new
namespace creation, you need to also dd the kuryrnetwork_population handler
@ -19,7 +21,9 @@ namespace creation, you need to also dd the kuryrnetwork_population handler
.. code-block:: ini
[kubernetes]
enabled_handlers=vif,lb,lbaasspec,policy,pod_label,namespace,kuryrnetworkpolicy,kuryrnetwork,kuryrnetwork_population,kuryrport
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,policy,
pod_label,namespace,kuryrnetworkpolicy,kuryrnetwork,
kuryrport,kuryrnetwork_population
After that, enable also the security group drivers for policies:
@ -82,7 +86,7 @@ to add the policy, pod_label and namespace handler and drivers with:
.. code-block:: bash
KURYR_ENABLED_HANDLERS=vif,lb,lbaasspec,policy,pod_label,namespace,kuryrnetworkpolicy,kuryrport
KURYR_ENABLED_HANDLERS=vif,endpoints,service,kuryrloadbalancer,policy,pod_label,namespace,kuryrnetworkpolicy,kuryrport
KURYR_SG_DRIVER=policy
KURYR_SUBNET_DRIVER=namespace


+ 4
- 2
doc/source/installation/ports-pool.rst View File

@ -169,7 +169,8 @@ subnet), the next handler needs to be enabled:
.. code-block:: ini
[kubernetes]
enabled_handlers=vif,lb,lbaasspec,namespace,*kuryrnetwork*
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,namespace,
*kuryrnetwork*
This can be enabled at devstack deployment time to by adding the next to the
@ -177,4 +178,5 @@ local.conf:
.. code-block:: bash
KURYR_ENABLED_HANDLERS=vif,lb,lbaasspec,namespace,*kuryrnetwork*
KURYR_ENABLED_HANDLERS=vif,endpoints,service,kuryrloadbalancer,namespace,
*kuryrnetwork*

+ 2
- 1
kuryr_kubernetes/config.py View File

@ -179,7 +179,8 @@ k8s_opts = [
cfg.ListOpt('enabled_handlers',
help=_("The comma-separated handlers that should be "
"registered for watching in the pipeline."),
default=['vif', 'lb', 'lbaasspec']),
default=['vif', 'endpoints', 'service', 'kuryrloadbalancer',
'kuryrport']),
cfg.BoolOpt('controller_ha',
help=_('Enable kuryr-controller active/passive HA. Only '
'supported in containerized deployments on Kubernetes '


Loading…
Cancel
Save