nested_doc: Fix lack of mention of service_subnet
Now that services are merged, it is necessary to have it documented in the nested guide, otherwise it can lead to configuration mistakes. Closes-Bug: #1677155 Change-Id: I0fb32bfa7fbe12ae468a745b60fcdad3d56999f6 Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
This commit is contained in:
parent
167d3ac010
commit
35006be8a5
|
@ -90,6 +90,7 @@ running. 4GB memory and 2 vCPUs, is the minimum resource requirement for the VM:
|
|||
pod_subnet = <UNDERCLOUD_SUBNET_FOR_PODS_UUID>
|
||||
project = <UNDERCLOUD_DEFAULT_PROJECT_UUID>
|
||||
worker_nodes_subnet = <UNDERCLOUD_SUBNET_WORKER_NODES_UUID>
|
||||
service_subnet = <UNDERCLOUD_SUBNET_FOR_SERVICES_UUID>
|
||||
|
||||
- Configure “pod_vif_driver” as “nested-vlan”::
|
||||
|
||||
|
|
Loading…
Reference in New Issue