mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-07 00:48:01 +01:00
29 lines
1011 B
Plaintext
29 lines
1011 B
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// *ingress-controller-dnsmgt.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="modifying-an-existing-ingress-controller_{context}"]
|
|
= Modifying an existing Ingress Controller
|
|
|
|
As a cluster administrator, you can modify an existing Ingress Controller to manually manage the DNS record lifecycle.
|
|
|
|
.Prerequisites
|
|
|
|
* Install the OpenShift CLI (`oc`).
|
|
* Log in as a user with `cluster-admin` privileges.
|
|
|
|
.Procedure
|
|
|
|
. Modify the chosen `IngressController` to set `dnsManagementPolicy`:
|
|
|
|
+
|
|
[source,terminal]
|
|
----
|
|
SCOPE=$(oc -n openshift-ingress-operator get ingresscontroller <name> -o=jsonpath="{.status.endpointPublishingStrategy.loadBalancer.scope}")
|
|
|
|
oc -n openshift-ingress-operator patch ingresscontrollers/<name> --type=merge --patch='{"spec":{"endpointPublishingStrategy":{"type":"LoadBalancerService","loadBalancer":{"dnsManagementPolicy":"Unmanaged", "scope":"${SCOPE}"}}}}'
|
|
----
|
|
|
|
. Optional: You can delete the associated DNS record in the cloud provider.
|