{"action":"created","issue":{"url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/54","repository_url":"https://api.github.com/repos/gardener/machine-controller-manager","labels_url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/54/labels{/name}","comments_url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/54/comments","events_url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/54/events","html_url":"https://github.com/gardener/machine-controller-manager/issues/54","id":305072750,"number":54,"title":"Node objects remain registered to Azure clusters after rolling update","user":{"login":"rfranzke","id":19169361,"avatar_url":"https://avatars1.githubusercontent.com/u/19169361?v=4","gravatar_id":"","url":"https://api.github.com/users/rfranzke","html_url":"https://github.com/rfranzke","followers_url":"https://api.github.com/users/rfranzke/followers","following_url":"https://api.github.com/users/rfranzke/following{/other_user}","gists_url":"https://api.github.com/users/rfranzke/gists{/gist_id}","starred_url":"https://api.github.com/users/rfranzke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rfranzke/subscriptions","organizations_url":"https://api.github.com/users/rfranzke/orgs","repos_url":"https://api.github.com/users/rfranzke/repos","events_url":"https://api.github.com/users/rfranzke/events{/privacy}","received_events_url":"https://api.github.com/users/rfranzke/received_events","type":"User","site_admin":false},"labels":[{"id":785766113,"url":"https://api.github.com/repos/gardener/machine-controller-manager/labels/bug","name":"bug","color":"ee0701","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-14T09:03:34Z","updated_at":"2018-03-14T12:12:20Z","closed_at":null,"author_association":"MEMBER","body":"When doing a rolling update on an Azure cluster, the machine controller does correctly roll the VMs, however, some `Node` objects of old VMs keep registered. On other clouds like AWS, GCP, OpenStack those objects are purged by the kube-controller-manager."},"comment":{"url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/comments/372999696","html_url":"https://github.com/gardener/machine-controller-manager/issues/54#issuecomment-372999696","issue_url":"https://api.github.com/repos/gardener/machine-controller-manager/issues/54","id":372999696,"user":{"login":"hardikdr","id":12736827,"avatar_url":"https://avatars1.githubusercontent.com/u/12736827?v=4","gravatar_id":"","url":"https://api.github.com/users/hardikdr","html_url":"https://github.com/hardikdr","followers_url":"https://api.github.com/users/hardikdr/followers","following_url":"https://api.github.com/users/hardikdr/following{/other_user}","gists_url":"https://api.github.com/users/hardikdr/gists{/gist_id}","starred_url":"https://api.github.com/users/hardikdr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hardikdr/subscriptions","organizations_url":"https://api.github.com/users/hardikdr/orgs","repos_url":"https://api.github.com/users/hardikdr/repos","events_url":"https://api.github.com/users/hardikdr/events{/privacy}","received_events_url":"https://api.github.com/users/hardikdr/received_events","type":"User","site_admin":false},"created_at":"2018-03-14T12:12:20Z","updated_at":"2018-03-14T12:12:20Z","author_association":"CONTRIBUTOR","body":"Yes, we saw this behavior in k8s 1.9.3 on azure, however it works fine with older versions. With k8s 1.8.7, it worked well, all the node-objects were removed by kube-controller-manager. \r\nWe shall follow up with the community on this."}}
{"actor":{"display_login":"hardikdr"}}