openstack/kuryr-kubernetes
Code Issues Proposed changes

Fix prepoulation of ports pool definition

Browse Source 
As part of the work to reduce OpenStack resource usage
the Namespace is only now handled when a Pod on Pods
Network is created in it. This new behavior also affects when
the ports pool prepopulation happens requiring update to
the docs.

Change-Id: Iac9d366b14e9e69d1a98da112ee53f97026c2f9d
This commit is contained in:
Maysa Macedo 2022-01-18 21:03:52 +00:00
parent 2ac0190bfa
commit 6199ad5739
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/installation/network_namespace.rst
View File

@ -16,9 +16,9 @@ the next steps are needed:
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
handler (more details on :doc:`./ports-pool`):
Note that if you also want to enable prepopulation of ports pools upon
creation of first pod on pods network in a namespace, you need to also
add the kuryrnetwork_population handler (more details on :doc:`./ports-pool`):
.. code-block:: ini

5
doc/source/installation/network_policy.rst
View File

@ -14,8 +14,9 @@ be found at :doc:`./devstack/containerized`):
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
Note that if you also want to enable prepopulation of ports pools upon creation
of first pod on pods network in a namespace, you need to also add the
kuryrnetwork_population handler
(more details on :doc:`./ports-pool`):
.. code-block:: ini