mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
46 lines
1.4 KiB
Plaintext
46 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * networking/understanding-external-dns-operator.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="nw-external-dns-operator_{context}"]
|
|
= Deploying the External DNS Operator
|
|
|
|
[role="_abstract"]
|
|
You can deploy the External DNS Operator on-demand from the Software Catalog. Deploying the External DNS Operator creates a `Subscription` object.
|
|
|
|
The External DNS Operator implements the External DNS API from the `olm.openshift.io` API group. The External DNS Operator updates services, routes, and external DNS providers.
|
|
|
|
.Prerequisites
|
|
|
|
* You have installed the `yq` CLI tool.
|
|
|
|
.Procedure
|
|
|
|
. Check the name of an install plan, such as `install-zcvlr`, by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n external-dns-operator get sub external-dns-operator -o yaml | yq '.status.installplan.name'
|
|
----
|
|
|
|
. Check if the status of an install plan is `Complete` by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n external-dns-operator get ip <install_plan_name> -o yaml | yq '.status.phase'
|
|
----
|
|
|
|
. View the status of the `external-dns-operator` deployment by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get -n external-dns-operator deployment/external-dns-operator
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY UP-TO-DATE AVAILABLE AGE
|
|
external-dns-operator 1/1 1 1 23h
|
|
----
|