{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/54482","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/54482/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/54482/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/54482/events","html_url":"https://github.com/kubernetes/kubernetes/issues/54482","id":268024543,"number":54482,"title":"k8s 1.8.1 hostname-override doesn't works?","user":{"login":"vasili439","id":23239384,"avatar_url":"https://avatars1.githubusercontent.com/u/23239384?v=4","gravatar_id":"","url":"https://api.github.com/users/vasili439","html_url":"https://github.com/vasili439","followers_url":"https://api.github.com/users/vasili439/followers","following_url":"https://api.github.com/users/vasili439/following{/other_user}","gists_url":"https://api.github.com/users/vasili439/gists{/gist_id}","starred_url":"https://api.github.com/users/vasili439/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vasili439/subscriptions","organizations_url":"https://api.github.com/users/vasili439/orgs","repos_url":"https://api.github.com/users/vasili439/repos","events_url":"https://api.github.com/users/vasili439/events{/privacy}","received_events_url":"https://api.github.com/users/vasili439/received_events","type":"User","site_admin":false},"labels":[{"id":105146071,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/bug","name":"kind/bug","color":"e11d21","default":false},{"id":328487998,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/aws","name":"sig/aws","color":"d2b48c","default":false},{"id":173493665,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/sig/node","name":"sig/node","color":"d2b48c","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2017-10-24T13:06:43Z","updated_at":"2018-03-21T19:38:53Z","closed_at":null,"author_association":"NONE","body":"**Is this a BUG REPORT or FEATURE REQUEST?**:\r\n\r\n/kind bug\r\n/sig aws\r\n\r\n\r\n**What happened**:\r\nTrying to start kubelet with --hostname-override=ip-172-28-68-60 but still see in the logs:\r\n```\r\nAttempting to register node ip-172-28-68-60.eu-west-1.compute.internal\r\nUnable to register node \"ip-172-28-68-60.eu-west-1.compute.internal\" with API server: nodes \"ip-172-28-68-60.eu-west-1.compute.internal\" is forbidden: node \"ip-172-28-68-60\" cannot modify node \"ip-172-28-68-60.eu-west-1.compute.internal\"\r\n```\r\nps aux:\r\nroot      4610  3.3  7.7 404596 78320 ?        Ssl  12:58   0:00 /usr/bin/kubelet ...... --hostname-override=ip-172-28-68-60\r\n\r\n**What you expected to happen**:\r\nHostname should be ip-172-28-68-60 instead of ip-172-28-68-60.eu-west-1.compute.internal\r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\nset\r\n--cloud-provider=aws --hostname-override=ip-172-28-68-60\r\nfor kubelet\r\n\r\n**Anything else we need to know?**:\r\n\r\n**Environment**:\r\n- Kubernetes version (use `kubectl version`):\r\nClient Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.1\", GitCommit:\"f38e43b221d08850172a9a4ea785a86a3ffa3b3a\", GitTreeState:\"clean\", BuildDate:\"2017-10-11T23:27:35Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"8\", GitVersion:\"v1.8.1\", GitCommit:\"f38e43b221d08850172a9a4ea785a86a3ffa3b3a\", GitTreeState:\"clean\", BuildDate:\"2017-10-11T23:16:41Z\", GoVersion:\"go1.8.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n\r\n- Cloud provider or hardware configuration**: aws\r\n\r\n- OS (e.g. from /etc/os-release):\r\nNAME=\"Ubuntu\"\r\nVERSION=\"16.04.2 LTS (Xenial Xerus)\"\r\nID=ubuntu\r\nID_LIKE=debian\r\nPRETTY_NAME=\"Ubuntu 16.04.2 LTS\"\r\nVERSION_ID=\"16.04\"\r\nHOME_URL=\"http://www.ubuntu.com/\"\r\nSUPPORT_URL=\"http://help.ubuntu.com/\"\r\nBUG_REPORT_URL=\"http://bugs.launchpad.net/ubuntu/\"\r\nVERSION_CODENAME=xenial\r\nUBUNTU_CODENAME=xenial\r\n\r\n- Kernel (e.g. `uname -a`): Linux ip-172-28-68-60 4.4.0-1038-aws #47-Ubuntu SMP Thu Sep 28 20:05:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux\r\n\r\n- Install tools:\r\n- Others:\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/375070306","html_url":"https://github.com/kubernetes/kubernetes/issues/54482#issuecomment-375070306","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/54482","id":375070306,"user":{"login":"daniilyar","id":849136,"avatar_url":"https://avatars2.githubusercontent.com/u/849136?v=4","gravatar_id":"","url":"https://api.github.com/users/daniilyar","html_url":"https://github.com/daniilyar","followers_url":"https://api.github.com/users/daniilyar/followers","following_url":"https://api.github.com/users/daniilyar/following{/other_user}","gists_url":"https://api.github.com/users/daniilyar/gists{/gist_id}","starred_url":"https://api.github.com/users/daniilyar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/daniilyar/subscriptions","organizations_url":"https://api.github.com/users/daniilyar/orgs","repos_url":"https://api.github.com/users/daniilyar/repos","events_url":"https://api.github.com/users/daniilyar/events{/privacy}","received_events_url":"https://api.github.com/users/daniilyar/received_events","type":"User","site_admin":false},"created_at":"2018-03-21T19:38:53Z","updated_at":"2018-03-21T19:38:53Z","author_association":"NONE","body":"We have this issue also. Our DEV Kubernetes live at baremetal env where kubelet `--hostname-override` option works fine and hence we are able to set node names to:\r\n```\r\nnode01-dev.<project_name>.com\r\nnode02-dev.<project_name>.com\r\nnode03-dev.<project_name>.com\r\n...\r\n```\r\n\r\nBut our staging and PROD envs are on AWS where we use `--provider aws`. In this case kubelet does not allow us to set node names according to our naming convention. In AWS we have the self-descriptive DNS names like `node02-staging.<project_name>.com` but cannot make node names to be equal to these DNS names because kubelet overrides it with ugly AWS `ip-xx-yy-zz.us-west-1.compute.internal`.\r\n\r\nImagine that you have a team of engineers and they receive an alert 'staging Kubernetes node 5 - disk full'. What would you like them to see when they run `kubectl get nodes` - `node05.staging - NotReady` or `ip-124-12-34.13.us-west-1.compute.internal - NotReady`? ;) Especially taking into account that `node05.staging` is a resolvable DNS name convenient for the team to use and that 'staging' word is in the node name so it is less possible for the engineer to accidentally go to a wrong env..\r\n\r\nWhat I want to say is that in AWS having a human-frindly CNAME record for each node and node name equal to this DNS record allows to make `kubectl get node` and `kubectl describe node` commands to give a more human-friendly representation of the cluster."}}
{"actor":{"display_login":"daniilyar"}}