mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
33 lines
1.5 KiB
Plaintext
33 lines
1.5 KiB
Plaintext
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="installation-gcp-enabling-user-managed-DNS_{context}"]
|
|
= Enabling a user-managed DNS
|
|
|
|
[role="_abstract"]
|
|
You can install a cluster with a domain name server (DNS) solution that you manage instead of the default cluster-provisioned DNS solution. As a result, you can manage the API and Ingress DNS records in your own system rather than adding the records to the DNS of the cloud.
|
|
|
|
For example, your organization's security policies might not allow the use of public DNS services such as {gcp-full} DNS. In such scenarios, you can use your own DNS service to bypass the public DNS service and manage your own DNS for the IP addresses of the API and Ingress services.
|
|
|
|
If you enable user-managed DNS during installation, the installation program provisions DNS records for the API and Ingress services only within the cluster. To ensure access from outside the cluster, you must provision the DNS records in an external DNS service of your choice for the API and Ingress services after installation.
|
|
|
|
.Prerequisites
|
|
|
|
* You installed the `jq` package.
|
|
|
|
.Procedure
|
|
* Before you deploy your cluster, use a text editor to open the `install-config.yaml` file and add the following stanza:
|
|
** To enable user-managed DNS:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
platform:
|
|
gcp:
|
|
userProvisionedDNS: Enabled
|
|
----
|
|
+
|
|
where:
|
|
|
|
`Enabled`:: Enables user-provisioned DNS management.
|
|
|
|
For information about provisioning your DNS records for the API server and the Ingress services, see "Provisioning your own DNS records".
|