{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kops/issues/2301","repository_url":"https://api.github.com/repos/kubernetes/kops","labels_url":"https://api.github.com/repos/kubernetes/kops/issues/2301/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kops/issues/2301/comments","events_url":"https://api.github.com/repos/kubernetes/kops/issues/2301/events","html_url":"https://github.com/kubernetes/kops/issues/2301","id":219875930,"number":2301,"title":"Proposal: Default nodeLabel/cloudLabel for instancegroup name","user":{"login":"zapman449","id":403763,"avatar_url":"https://avatars1.githubusercontent.com/u/403763?v=4","gravatar_id":"","url":"https://api.github.com/users/zapman449","html_url":"https://github.com/zapman449","followers_url":"https://api.github.com/users/zapman449/followers","following_url":"https://api.github.com/users/zapman449/following{/other_user}","gists_url":"https://api.github.com/users/zapman449/gists{/gist_id}","starred_url":"https://api.github.com/users/zapman449/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zapman449/subscriptions","organizations_url":"https://api.github.com/users/zapman449/orgs","repos_url":"https://api.github.com/users/zapman449/repos","events_url":"https://api.github.com/users/zapman449/events{/privacy}","received_events_url":"https://api.github.com/users/zapman449/received_events","type":"User","site_admin":false},"labels":[{"id":527816559,"url":"https://api.github.com/repos/kubernetes/kops/labels/good-starter-issue","name":"good-starter-issue","color":"0e8a16","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2017-04-06T12:02:00Z","updated_at":"2018-05-25T01:45:10Z","closed_at":null,"author_association":"NONE","body":"In order to allow the external world to interact with the same structures that kops uses, it would be helpful if there was a way to identify members of those structures.\r\n\r\nSpecifically, there should be a default nodeLabel and cloudLabel for instance groups that have the name of the instancegroup in there.  I propose the following convention (which is open for debate):\r\n\r\n```\r\nnodeLabels:\r\n  kops.kubernetes.io/instancegroup: nodes\r\ncloudLabels:\r\n  kops.kubernetes.io/instancegroup: nodes\r\n```\r\n\r\nSimilar for HA masters:\r\n\r\n```\r\nnodeLabels:\r\n  kops.kubernetes.io/instancegroup: master-us-west-1a-2\r\ncloudLabels:\r\n  kops.kubernetes.io/instancegroup: master-us-west-1a-2\r\n```\r\n\r\nThis would facilitate kops customers writing tools that need to work with specific instance groups, whether within kubernetes or within AWS."},"comment":{"url":"https://api.github.com/repos/kubernetes/kops/issues/comments/391916448","html_url":"https://github.com/kubernetes/kops/issues/2301#issuecomment-391916448","issue_url":"https://api.github.com/repos/kubernetes/kops/issues/2301","id":391916448,"user":{"login":"fejta-bot","id":30488982,"avatar_url":"https://avatars1.githubusercontent.com/u/30488982?v=4","gravatar_id":"","url":"https://api.github.com/users/fejta-bot","html_url":"https://github.com/fejta-bot","followers_url":"https://api.github.com/users/fejta-bot/followers","following_url":"https://api.github.com/users/fejta-bot/following{/other_user}","gists_url":"https://api.github.com/users/fejta-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/fejta-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fejta-bot/subscriptions","organizations_url":"https://api.github.com/users/fejta-bot/orgs","repos_url":"https://api.github.com/users/fejta-bot/repos","events_url":"https://api.github.com/users/fejta-bot/events{/privacy}","received_events_url":"https://api.github.com/users/fejta-bot/received_events","type":"User","site_admin":false},"created_at":"2018-05-25T01:45:10Z","updated_at":"2018-05-25T01:45:10Z","author_association":"NONE","body":"Issues go stale after 90d of inactivity.\nMark the issue as fresh with `/remove-lifecycle stale`.\nStale issues rot after an additional 30d of inactivity and eventually close.\n\nIf this issue is safe to close now please do so with `/close`.\n\nSend feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n/lifecycle stale"}}
{"actor":{"display_login":"fejta-bot"}}