kube-dns clusterip about release

[colemickens]

What is the question? (edit: sorry, just saw it finally -- the cluster ip in the kubeadm conf differs from the actual service clusterip in the cluster.)

[autostatic]

I had the same issue. After updating the kubelet package from the Google Kubernetes repo from 1.4.3 to 1.4.4 on Ubuntu 16.04 new pods could not resolve anything. Turned out that someone or something decided to change the cluster-dns IP in /etc/systemd/system/kubelet.service.d/10-kubeadm.conf from 100.64.0.10 to 10.96.0.10. After changing this back and restarting the Kubelet services everything worked again.
So if possible please add a conffiles file to the Debian based distribution debian directories that includes at least /etc/systemd/system/kubelet.service.d/10-kubeadm.conf. Thanks in advance.

[fejta-bot]

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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