This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.Chapter 4. DNS Operator in OpenShift Container Platform
The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods, enabling DNS-based Kubernetes Service discovery in OpenShift.
4.1. DNS Operator Copy linkLink copied to clipboard!
The DNS Operator implements the dns
API from the operator.openshift.io
API group. The operator deploys CoreDNS using a DaemonSet, creates a Service for the DaemonSet, 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:oc get -n openshift-dns-operator deployment/dns-operator
$ oc get -n openshift-dns-operator deployment/dns-operator NAME READY UP-TO-DATE AVAILABLE AGE dns-operator 1/1 1 1 23h
Copy to Clipboard Copied! Toggle word wrap Toggle overflow 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:oc get clusteroperator/dns
$ oc get clusteroperator/dns NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE dns 4.1.0-0.11 True False False 92m
Copy to Clipboard Copied! Toggle word wrap Toggle overflow AVAILABLE
,PROGRESSING
andDEGRADED
provide information about the status of the operator.AVAILABLE
isTrue
when at least 1 pod from the CoreDNS DaemonSet is reporting anAvailable
status condition.
4.2. View the default DNS Copy linkLink copied to clipboard!
Every new OpenShift Container Platform installation has a dns.operator
named default
. It cannot be customized, replaced, or supplemented with additional dnses
.
Procedure
Use the
oc describe
command to view the defaultdns
:Copy to Clipboard Copied! Toggle word wrap Toggle overflow To find the Service CIDR of your cluster, use the
oc get
command:oc get networks.config/cluster -o jsonpath='{$.status.serviceNetwork}'
$ oc get networks.config/cluster -o jsonpath='{$.status.serviceNetwork}' [172.30.0.0/16]
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Configuration of the CoreDNS Corefile or Kubernetes plugin is not supported.
4.3. DNS Operator status Copy linkLink copied to clipboard!
You can inspect the status and view the details of the DNS Operator using the oc describe
command.
Procedure
View the status of the DNS Operator:
oc describe clusteroperators/dns
$ oc describe clusteroperators/dns
4.4. DNS Operator logs Copy linkLink copied to clipboard!
You can view DNS Operator logs by using the oc logs
command.
Procedure
View the logs of the DNS Operator:
oc logs --namespace=openshift-dns-operator deployment/dns-operator
$ oc logs --namespace=openshift-dns-operator deployment/dns-operator