- Currently the VPCs accounts are configured so that they allow DNS resolving via our enterprise DNS.
- As a team it is not possible to change the DHCP option set as this stuff is centrally handled because of company rules.
- On OpenShift 3 this was solved this issue by using dnsmasq in order to additionally configure the AWS DNS server for the OpenShift 3 RHEL machines.
- On OpenShift 4,, CoreDNS replaces dnsmasq and so far there is no way to provide other name servers to the DNS configuration of the operating systems other than those provided via DHCP.
- For enterprise customers that cannot change DHCP option sets, it would be very cool if it was possible to pass additional name server IPs to the OpenShift 4 bootstrapping procedure via the install-config.json file.
- Red Hat OpenShift Container Platform(OCS) 4.x
- Amazon Web Services(AWS)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.