mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-06 06:46:26 +01:00
49 lines
1.4 KiB
Plaintext
49 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * networking/dns/dns-operator.adoc
|
|
|
|
[id="dns-operator_{context}"]
|
|
= DNS Operator
|
|
|
|
The DNS Operator implements the `dns` API from the `operator.openshift.io` API
|
|
group. The operator deploys CoreDNS using a daemon set, creates a Service for
|
|
the daemon set, and configures the kubelet to instruct pods to use the CoreDNS
|
|
Service IP for name resolution.
|
|
|
|
.Procedure
|
|
The DNS Operator is deployed during installation as a Kubernetes `Deployment`.
|
|
|
|
. Use the `oc get` command to view the Deployment status:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get -n openshift-dns-operator deployment/dns-operator
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY UP-TO-DATE AVAILABLE AGE
|
|
dns-operator 1/1 1 1 23h
|
|
----
|
|
ClusterOperator is the Custom Resource object which holds the current state
|
|
of an operator. This object is used by operators to convey their state to
|
|
the rest of the cluster.
|
|
|
|
. Use the `oc get` command to view the state of the DNS Operator:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusteroperator/dns
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
|
|
dns 4.1.0-0.11 True False False 92m
|
|
----
|
|
+
|
|
`AVAILABLE`, `PROGRESSING` and `DEGRADED` provide information about the status of
|
|
the operator. `AVAILABLE` is `True` when at least 1 pod from the CoreDNS DaemonSet
|
|
is reporting an `Available` status condition.
|