coredns and kube-dns-autoscaler pending
Summary
node.cloudprovider.kubernetes.io/uninitialized: true prevents scheduling of core functionalityContent
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 {node.cloudprovider.kubernetes.io/uninitialized: 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
Tagged:
0