{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/29033","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/29033/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/29033/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/29033/events","html_url":"https://github.com/kubernetes/kubernetes/issues/29033","id":165886239,"number":29033,"title":"Have kubelet delete all pods","user":{"login":"vishh","id":7063592,"avatar_url":"https://avatars.githubusercontent.com/u/7063592?v=3","gravatar_id":"","url":"https://api.github.com/users/vishh","html_url":"https://github.com/vishh","followers_url":"https://api.github.com/users/vishh/followers","following_url":"https://api.github.com/users/vishh/following{/other_user}","gists_url":"https://api.github.com/users/vishh/gists{/gist_id}","starred_url":"https://api.github.com/users/vishh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vishh/subscriptions","organizations_url":"https://api.github.com/users/vishh/orgs","repos_url":"https://api.github.com/users/vishh/repos","events_url":"https://api.github.com/users/vishh/events{/privacy}","received_events_url":"https://api.github.com/users/vishh/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/priority/P1","name":"priority/P1","color":"eb6420"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/node","name":"team/node","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/kubernetes/kubernetes/milestones/22","html_url":"https://github.com/kubernetes/kubernetes/milestones/v1.4","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/milestones/22/labels","id":1777384,"number":22,"title":"v1.4","description":"https://github.com/kubernetes/features/blob/master/release-1.4/Release-1.4.md","creator":{"login":"bgrant0607","id":7725777,"avatar_url":"https://avatars.githubusercontent.com/u/7725777?v=3","gravatar_id":"","url":"https://api.github.com/users/bgrant0607","html_url":"https://github.com/bgrant0607","followers_url":"https://api.github.com/users/bgrant0607/followers","following_url":"https://api.github.com/users/bgrant0607/following{/other_user}","gists_url":"https://api.github.com/users/bgrant0607/gists{/gist_id}","starred_url":"https://api.github.com/users/bgrant0607/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bgrant0607/subscriptions","organizations_url":"https://api.github.com/users/bgrant0607/orgs","repos_url":"https://api.github.com/users/bgrant0607/repos","events_url":"https://api.github.com/users/bgrant0607/events{/privacy}","received_events_url":"https://api.github.com/users/bgrant0607/received_events","type":"User","site_admin":false},"open_issues":241,"closed_issues":242,"state":"open","created_at":"2016-05-19T18:50:19Z","updated_at":"2016-08-19T18:29:49Z","due_on":"2016-09-15T00:00:00Z","closed_at":null},"comments":38,"created_at":"2016-07-15T22:03:41Z","updated_at":"2016-08-19T18:35:01Z","closed_at":null,"body":"As of now kubelet deletes pods that have a graceful termination period > 0 seconds. Why not have kubelet delete all pods, even ones that have graceful termination == 0 ?\r\n\r\nHaving kubelet delete pod objects will make it possible to identify pods that are still being cleaned up kubelet, and hence occupying some resources. Ideally, a pod should not be considered as deleted until all its resources have been reclaimed, including volumes. Having kubelet delete the pod object after it has successfully cleaned up a pod on the node is ideal.\r\n\r\nThis feature will make it possible to introduce pod level cgroups in kubelet. Pod level resources cannot be reclaimed until volumes belonging to a pod have been removed successfully, at-least tmpfs based ones to begin with. Until the resources are reclaimed, we don't want the scheduler to incorrectly assume that those *yet to be reclaimed* resources are available on the node.\r\n\r\ncc @davidopp who proposed this idea.\r\n\r\ncc @smarterclayton @kubernetes/sig-node \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/241099204","html_url":"https://github.com/kubernetes/kubernetes/issues/29033#issuecomment-241099204","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/29033","id":241099204,"user":{"login":"smarterclayton","id":1163175,"avatar_url":"https://avatars.githubusercontent.com/u/1163175?v=3","gravatar_id":"","url":"https://api.github.com/users/smarterclayton","html_url":"https://github.com/smarterclayton","followers_url":"https://api.github.com/users/smarterclayton/followers","following_url":"https://api.github.com/users/smarterclayton/following{/other_user}","gists_url":"https://api.github.com/users/smarterclayton/gists{/gist_id}","starred_url":"https://api.github.com/users/smarterclayton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smarterclayton/subscriptions","organizations_url":"https://api.github.com/users/smarterclayton/orgs","repos_url":"https://api.github.com/users/smarterclayton/repos","events_url":"https://api.github.com/users/smarterclayton/events{/privacy}","received_events_url":"https://api.github.com/users/smarterclayton/received_events","type":"User","site_admin":false},"created_at":"2016-08-19T18:35:01Z","updated_at":"2016-08-19T18:35:01Z","body":"The scenario Derek described to me as being the concern, seems like a\ndetail of the Kubelet that should not be leaking out to the rest of the\nsystem.  The propagation of info from kubelet -> scheduler is always going\nto be susceptible to delay and inaccuracy - I don't think users force\ndeleting pods causes that problem or lifts the Kubelet from tolerating and\nadapting to that latency.\n\nOn Fri, Aug 19, 2016 at 2:33 PM, Derek Carr <notifications@github.com>\nwrote:\n\n> Thinking on this more, I think #29033 (comment)\n> <https://github.com/kubernetes/kubernetes/issues/29033#issuecomment-241098465>\n> should be possible without a change to the API model. kubelet knows the\n> state of cgroups on the node.\n>\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/kubernetes/kubernetes/issues/29033#issuecomment-241098769>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/ABG_p_FIFcnmgcKl-vITR-h4YopKSfFWks5qhfb8gaJpZM4JN0ox>\n> .\n>\n"}}
{"actor":{"display_login":"smarterclayton"}}