openshift/installer
1
0
Fork 0
mirror of https://github.com/openshift/installer.git synced 2026-02-05 15:47:14 +01:00
Code Issues Releases Activity

external dns

Browse Source
This commit is contained in:
Emilio Garcia
2019-11-04 15:58:12 -05:00
parent 6fd58226b0
commit 3de4da3fbc
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/user/openstack/customization.md
View File

@@ -7,7 +7,7 @@ Beyond the [platform-agnostic `install-config.yaml` properties](../customization
* `cloud` (required string): The name of the OpenStack cloud to use from `clouds.yaml`.
* `computeFlavor` (required string): The OpenStack flavor to use for compute and control-plane machines.
This is currently required, but has lower precedence than [the `type` property](#machine-pools) on [the `compute` and `controlPlane` machine-pools](../customization.md#platform-customization).
* `externalDNS` (optional string slice): The IP addresses of DNS servers to be used for the DNS resolution of all instances in the cluster (for example, `["1.1.1.1", "8.8.8.8"]`).
* `externalDNS` (optional list of strings): The IP addresses of DNS servers to be used for the DNS resolution of all instances in the cluster
* `externalNetwork` (required string): The OpenStack external network name to be used for installation.
* `lbFloatingIP` (required string): Existing Floating IP to associate with the API load balancer.
* `octaviaSupport` (optional string): Whether OpenStack supports Octavia (`1` for true or `0` for false)
@@ -40,6 +40,9 @@ platform:
cloud: mycloud
computeFlavor: m1.s2.xlarge
externalNetwork: external
externalDNS:
- "8.8.8.8"
- "192.168.1.12"
lbFloatingIP: 128.0.0.1
region: region1
pullSecret: '{"auths": ...}'

2
docs/user/openstack/known-issues.md
View File

@@ -28,7 +28,7 @@ clusterNetwork: 10.128.0.0/14
Some OpenStack clouds do not set default DNS servers for the newly created subnets. In this case, the bootstrap node may fail to resolve public name records to download the OpenShift images or resolve the OpenStack API endpoints.
If you are in this situation, you can add resolvers to the provisioned subnet by setting the [`externalDNS` property in `install-config.yaml`](./customization.md#cluster-scoped-properties).
If you are having this problem in the IPI installer, you will need to set the [`externalDNS` property in `install-config.yaml`](./customization.md#cluster-scoped-properties).
Alternatively, for UPI, you will need to [set the subnet DNS resolvers](./install_upi.md#subnet-dns-optional).