Fix prepoulation of ports pool definition
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:
parent
2ac0190bfa
commit
6199ad5739
@ -16,9 +16,9 @@ the next steps are needed:
|
|||||||
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,namespace,
|
enabled_handlers=vif,endpoints,service,kuryrloadbalancer,namespace,
|
||||||
kuryrnetwork,kuryrport
|
kuryrnetwork,kuryrport
|
||||||
|
|
||||||
Note that if you also want to enable prepopulation of ports pools upon new
|
Note that if you also want to enable prepopulation of ports pools upon
|
||||||
namespace creation, you need to also add the kuryrnetwork_population
|
creation of first pod on pods network in a namespace, you need to also
|
||||||
handler (more details on :doc:`./ports-pool`):
|
add the kuryrnetwork_population handler (more details on :doc:`./ports-pool`):
|
||||||
|
|
||||||
.. code-block:: ini
|
.. code-block:: ini
|
||||||
|
|
||||||
|
@ -14,8 +14,9 @@ be found at :doc:`./devstack/containerized`):
|
|||||||
pod_label,namespace,kuryrnetwork,kuryrnetworkpolicy,
|
pod_label,namespace,kuryrnetwork,kuryrnetworkpolicy,
|
||||||
kuryrport
|
kuryrport
|
||||||
|
|
||||||
Note that if you also want to enable prepopulation of ports pools upon new
|
Note that if you also want to enable prepopulation of ports pools upon creation
|
||||||
namespace creation, you need to also dd the kuryrnetwork_population handler
|
of first pod on pods network in a namespace, you need to also add the
|
||||||
|
kuryrnetwork_population handler
|
||||||
(more details on :doc:`./ports-pool`):
|
(more details on :doc:`./ports-pool`):
|
||||||
|
|
||||||
.. code-block:: ini
|
.. code-block:: ini
|
||||||
|
Loading…
x
Reference in New Issue
Block a user