Skip to content
The Cluster DNS Operator manages cluster DNS services for OpenShift
Branch: master
Clone or download
openshift-merge-robot Merge pull request #99 from danehans/degrade_status
Moves Operator Failing status to Degraded
Latest commit 03112ff Apr 24, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
assets/dns Integrate coredns metrics with openshift-monitoring Apr 23, 2019
cmd/dns-operator
hack Integrate coredns metrics with openshift-monitoring Apr 23, 2019
manifests Integrate coredns metrics with openshift-monitoring Apr 23, 2019
pkg
test/e2e Rename 'Cluster DNS' references to 'DNS' Apr 10, 2019
vendor Bump openshift/api dep to support Degraded condition Apr 23, 2019
.gitignore
Dockerfile
Dockerfile.rhel7 Rename cluster-dns-operator binary to dns-operator Apr 10, 2019
Gopkg.lock Bump openshift/api dep to support Degraded condition Apr 23, 2019
Gopkg.toml
HACKING.md Rename DNS owning and daemonset labels Apr 10, 2019
LICENSE Add license file Aug 16, 2018
Makefile Rename cluster-dns-operator binary to dns-operator Apr 10, 2019
OWNERS Update OWNERS Dec 20, 2018
README.md

README.md

The DNS Operator

The DNS Operator deploys and manages CoreDNS to provide a name resolution service to pods that enables DNS-based Kubernetes Service discovery in OpenShift.

The operator tries to be useful out of the box by creating a working default deployment based on the cluster's configuration.

  • The default cluster domain is cluster.local.
  • Configuration of the CoreDNS Corefile or kubernetes plugin is not yet supported.

How it works

The DNS Operator manages CoreDNS as a Kubernetes DaemonSet exposed as a Service with a static IP — CoreDNS runs on all nodes in the cluster.

How to help

See HACKING.md for development topics.

Reporting issues

Bugs are tracked in Bugzilla.

You can’t perform that action at this time.