{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/kubeadm/issues/411","repository_url":"https://api.github.com/repos/kubernetes/kubeadm","labels_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/411/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/411/comments","events_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/411/events","html_url":"https://github.com/kubernetes/kubeadm/issues/411","id":252588453,"number":411,"title":"allow join to master dns name","user":{"login":"kapilt","id":21650,"avatar_url":"https://avatars3.githubusercontent.com/u/21650?v=4","gravatar_id":"","url":"https://api.github.com/users/kapilt","html_url":"https://github.com/kapilt","followers_url":"https://api.github.com/users/kapilt/followers","following_url":"https://api.github.com/users/kapilt/following{/other_user}","gists_url":"https://api.github.com/users/kapilt/gists{/gist_id}","starred_url":"https://api.github.com/users/kapilt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kapilt/subscriptions","organizations_url":"https://api.github.com/users/kapilt/orgs","repos_url":"https://api.github.com/users/kapilt/repos","events_url":"https://api.github.com/users/kapilt/events{/privacy}","received_events_url":"https://api.github.com/users/kapilt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-08-24T12:40:39Z","updated_at":"2017-08-24T12:40:39Z","closed_at":null,"body":"i'm using kubeadm in a cloud environment, one of the challenges is that join will always use the ip address of the master instead of a passed in dns name (master cert also with subject alt to include dns name). the join ends up writing out the master ip to the kubelet.conf which complicates rotation/restoration of the master. given the symmetric secret, and the ca hash work being done in\r\nhttps://docs.google.com/document/d/1SP4P7LJWSA8vUXj27UvKdVEdhpo5Fp0QHNo4TXvLQbw/edit?ts=5971498a#heading=h.5bejulk96xxi\r\n\r\nis there any reason why kubeadm couldn't support using the actual value passed (ip or dns per use choice) instead of forcing ip usage?\r\n\r\nkubeadm version - 1.7.4"}}
{"actor":{"display_login":"kapilt"}}