{"action":"closed","issue":{"url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws/issues/466","repository_url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws","labels_url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws/issues/466/labels{/name}","comments_url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws/issues/466/comments","events_url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws/issues/466/events","html_url":"https://github.com/zalando-incubator/kubernetes-on-aws/issues/466","id":237890568,"number":466,"title":"kube-node-drainer and reboots","user":{"login":"tanuck","id":289004,"avatar_url":"https://avatars1.githubusercontent.com/u/289004?v=4","gravatar_id":"","url":"https://api.github.com/users/tanuck","html_url":"https://github.com/tanuck","followers_url":"https://api.github.com/users/tanuck/followers","following_url":"https://api.github.com/users/tanuck/following{/other_user}","gists_url":"https://api.github.com/users/tanuck/gists{/gist_id}","starred_url":"https://api.github.com/users/tanuck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tanuck/subscriptions","organizations_url":"https://api.github.com/users/tanuck/orgs","repos_url":"https://api.github.com/users/tanuck/repos","events_url":"https://api.github.com/users/tanuck/events{/privacy}","received_events_url":"https://api.github.com/users/tanuck/received_events","type":"User","site_admin":false},"labels":[{"id":461369049,"url":"https://api.github.com/repos/zalando-incubator/kubernetes-on-aws/labels/question","name":"question","color":"cc317c","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-06-22T15:47:16Z","updated_at":"2017-08-01T08:34:45Z","closed_at":"2017-08-01T08:34:45Z","body":"Hi,\r\n\r\nI had a question about your `kube-node-drainer` systemd service that forms part of your worker/master userdata. I've used it as inspiration for a similar service to solve a problem with worker reboots due to os updates. However, when the workers restart and return to a `Ready` state, they remain with `SchedulingDisabled`. Is that the intended behaviour for it?\r\n\r\nThanks,"}}
{"actor":{"display_login":"tanuck"}}