@@ -25,9 +25,9 @@ connected by a private _software defined network_ (SDN) which can be
2525implemented either with http://openvswitch.org/[OpenVSwitch] or https://github.com/coreos/flannel[Flannel].
2626
2727A _bastion server_ is used to control the host and service
28- configuration. It can also run local DNS services as
29- needed. The host and service configuration is run using
30- https://www.ansible.com/[Ansible] playbooks executed from the bastion host.
28+ configuration. The host and service configuration is run using
29+ https://www.ansible.com/[Ansible] playbooks executed from the bastion
30+ host.
3131
3232_Bastion server_, _master nodes_ and _infra nodes_ is also given a _floating IP_
3333address on the public network. This provides direct access to the
@@ -68,6 +68,28 @@ inter-node communication).
6868
6969CentOS and RHEL are the only tested distros for now.
7070
71+ === DNS Server
72+
73+ The OpenShift installer requires that all nodes be reachable via their
74+ hostnames. Since OpenStack does not currently provide an internal name
75+ resolution, this needs to be done with an external DNS service that
76+ all nodes use via the `dns_nameserver` parameter.
77+
78+ In a production deployment this would be your existing DNS, but if you
79+ don't have the ability to update it to add new name records, you will
80+ have to deploy one yourself.
81+
82+ We have provided a separate repository that can deploy a DNS server
83+ suitable for OpenShift:
84+
85+ https://github.com/openshift/openshift-ansible-contrib/tree/master/reference-architecture/osp-dns
86+
87+ NOTE: If your DNS supports dynamic updates via RFC 2136, you can pass
88+ the update key to the Heat stack and all nodes will register
89+ themselves as they come up. Otherwise, you will have to update your
90+ DNS records manually.
91+
92+
7193=== Red Hat Software Repositories
7294
7395When installing OpenShift Container Platform on RHEL the OpenShift and
@@ -480,6 +502,17 @@ The above DNS records should be set on the DNS server authoritative for the
480502domain used in OpenShift cluster (`example.com` in the example above).
481503====
482504
505+
506+ === Dynamic DNS Updates
507+
508+ If your DNS servers support dynamic updates (as defined in RFC 2136),
509+ you can pass the update key in the `dns_update_key` parameter and each
510+ node will register its internal IP address to all the DNS servers in
511+ the `dns_nameserver` list.
512+
513+ You will still need to set the API and wildcard entries, though.
514+
515+
483516== Retrieving the CA certificate
484517
485518You can retrieve the CA certificate that was generated during the OpenShift
0 commit comments