Truncated Hostname kube-controller-manager
wolstena opened this issue · 4 comments
I have been in the process of creating a new cluster using kube-aws 0.14.2. And it seemed to be failing randomly. I found in the logs the hostname for the controller is too long.
Nov 05 23:42:56 ip-10-50-14-49.acc1.central1.cc sh[2017]: E1105 23:42:56.434543 2017 kubelet_pods.go:388] hostname for pod:"kube-controller-manager-ip-10-50-14-49.ca-central-1.compute.internal" was longer than 63. Truncated hostname to :"kube-controller-manager-ip-10-50-14-49.ca-central-1.compute.int"
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
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
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
@fejta-bot: Closing this issue.
In response to this:
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
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.