Add step for overcloud DNS setup in TLS everywhere doc
This step was missing, as using the DNSServers parameter is not enough. Change-Id: I0c80375819db6f5214048549c662cafd74a9798c
This commit is contained in:
parent
ace9d31da2
commit
ff47eec75c
|
@ -148,6 +148,9 @@ like this::
|
|||
|
||||
Remembering that optionally we can set other nameservers with this parameter.
|
||||
|
||||
You'll also need to add set the DNS server for the ctlplane network to point to
|
||||
FreeIPA as described in :ref:`basic-deployment-cli-configure-namserver`.
|
||||
|
||||
To tell the overcloud deployment to deploy the keystone endpoints (and
|
||||
references) using DNS names instead of IPs, we need to add the following
|
||||
environment to our overcloud deployment::
|
||||
|
|
|
@ -359,6 +359,8 @@ In addition, there are profile-specific flavors created which can be used with
|
|||
the profile-matching feature. For more details on deploying with profiles,
|
||||
see :doc:`../advanced_deployment/profile_matching`.
|
||||
|
||||
.. _basic-deployment-cli-configure-namserver:
|
||||
|
||||
Configure a nameserver for the Overcloud
|
||||
----------------------------------------
|
||||
|
||||
|
|
Loading…
Reference in New Issue