kubernetes-retired/kubeadm-dind-cluster

v1.12 kubeadm template is not setting cluster dns

jlyheden opened this issue · 3 comments

This causes the dind cluster with a custom service cidr to have broken dns, ie the default cluster-dns from kubelet (10.96.0.10) will be injected in resolv.conf in the pods.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Closing as this project is being deprecated and retired in favor of KinD.

Please see this issue for more details:
kubernetes/org#1016

/close

@mrbobbytables: Closing this issue.

In response to this:

Closing as this project is being deprecated and retired in favor of KinD.

Please see this issue for more details:
kubernetes/org#1016

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.