Document usage of pod dependencies

Replace references to daemonset dependencies with pod dependencies in
docs.

Change-Id: I252089006929d7e218ebfc4f98d49c4650143a7e
This commit is contained in:
Sean Eagan 2018-03-19 10:26:03 -05:00
parent ac2b8a090b
commit a44ab387b5
2 changed files with 29 additions and 15 deletions

View File

@ -137,9 +137,11 @@ for the L2 agent daemonset:
endpoint: internal
- service: compute
endpoint: internal
daemonset:
# this should be set to corresponding neutron L2 agent
- neutron-ovs-agent
pod:
# this should be set to corresponding neutron L2 agent
- labels:
application: neutron
component: neutron-ovs-agent
There is also a need for DHCP agent to pass ovs agent config file
(in :code:`neutron/templates/bin/_neutron-dhcp-agent.sh.tpl`):
@ -317,14 +319,20 @@ and use this `neutron/values.yaml` override:
backend: linuxbridge
dependencies:
dhcp:
daemonset:
- neutron-lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
metadata:
daemonset:
- neutron-lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
l3:
daemonset:
- neutron-lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
conf:
neutron:
DEFAULT

View File

@ -98,14 +98,20 @@ updated to reflect the new kind on L2 agent:
dependencies:
dhcp:
daemonset:
- lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
metadata:
daemonset:
- lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
l3:
daemonset:
- lb-agent
pod:
- labels:
application: neutron
component: neutron-lb-agent
LinuxBridge should be also enabled in :code:`manifests` section: