Bug 1790298
| Summary: | [ShiftStack 4.2 on OSP13] install-config.yaml is missing option for customized DNS server | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Robin Cernin <rcernin> |
| Component: | Installer | Assignee: | Max Bridges <mbridges> |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> |
| Status: | CLOSED CURRENTRELEASE | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | eduen, hasha, scuppett, tsedovic, vigoyal |
| Version: | 4.2.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
Feature: Configuring custom DNS nameservers for the OpenShift nodes
Reason: Some OpenStack deployments do not set a default nameserver for its servers. In such deployments, the OpenStack tenant is expected to configure their own resolvers on the Neutron subnet or Nova server.
Running the OpenShift installer against such a deployment requires setting these servers in install-config.yaml. Otherwise, the deployment will fail when trying to pull the OpenShift images during bootstrapping phase.
Result:
If the OpenStack server does not configure default nameservers or if you want to change them, it is possible to set the `platform.openstack.externalDNS` field in install-config.yaml. This will add the specified DNS servers to the nodes Neutron subnet and the Nova servers created in the subnet will use them for DNS.
For example:
platform:
openstack:
externalDNS:
- 203.0.113.23
- 203.0.113.42
This option has existed since the 4.2 release.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-22 00:20:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Robin Cernin
2020-01-13 04:04:12 UTC
Moving to the active development branch (4.4). For any needed fixes where backports are required/requested, BZ clones will be created targeting those specific z-stream releases. Robin Cernin: this functionality exists since 4.2. You can add the DNS servers in the `platform.openstack.externalDNS` field in install-config.yaml:
platform:
openstack:
externalDNS:
- 203.0.113.23
- 203.0.113.42
They will be set on the subnet in the same way as `openstack subnet set --dns-nameserver` would do. This is documented upstream in the Customization page:
https://github.com/openshift/installer/blob/master/docs/user/openstack/customization.md
But it looks like it's missing from the product documentation. This should be addressed by the docs team, I've filled out the Doc Text field.
Eric Duen: do you know how to tag in the docs folks? Should I assign this bug to Max Bridges?
Assigned to Max. Updating the target to 4.2z, since it is a defect in 4.2 docs. Max, I reassigned to you, please take a look and update the BZ accordingly (priority, target, etc.) Doesn't look like too hairy of an update to make, but we generally allow the DPM to set those fields. I'll make a first pass on this this week, though. :) How's this PR look, Tomas? Verified PR https://docs.openshift.com/container-platform/4.2/installing/installing_openstack/installing-openstack-installer-custom.html#installation-configuration-parameters_installing-openstack-installer-custom Waiting on update to portal. vigoyal confirms that this is live on the portal at the address in comment 1. Closing. |