How to set CoreDNS Operator into unmanaged state

Solution Verified - Updated -


During troubleshooting a Red Hat Support Engineer has requested changes be performed to the CoreDNS configurations and deployments. These Configurations are controlled by the OpenShift Cluster DNS Operator, which manages most of the resources within the openshift-dns Namespace.

To perform changes to these managed resources, the Cluster DNS Operator must be disabled first.

The Cluster Version Operator (CVO) manages the Cluster DNS Operator and most of the resources in the openshift-dns-operator Namespace. Therefore the Cluster DNS Operator must be removed from the CVO management before it can be disabled to allow changes to the DNS configurations.

NOTE: This should not be performed without the request of an Red Hat OpenShift Support Engineers request and will result in the OpenShift Cluster in an unsupported state


  • OpenShift 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content