You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

coredns and kube-dns-autoscaler pending

Received Response
edited Aug 9, 2021 6:53PM in Containers and Kubernetes 1 comment

Summary true prevents scheduling of core functionality


I have set up a new OKE cluster with a node pool consisting of 3 nodes and everything running in public subnets (for now).

The following seem to be working:

  • csi-oci-node
  • kube-flannel-ds
  • kube-proxy
  • proxymux-client

However, coredns and kube-dns-autoscaler fail to launch:

Warning FailedScheduling 17m default-scheduler 0/3 nodes are available: 3 node(s) had taint { true}, that the pod didn't tolerate.

I would expect this to work out of the box on a managed cluster.

Has anyone experienced similar issues? How did you fix them?


Any pointers are appreciated


Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!