{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/31778","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/31778/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/31778/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/31778/events","html_url":"https://github.com/kubernetes/kubernetes/issues/31778","id":174256990,"number":31778,"title":"eviction-hard setting doesnt prevent pods from being re-scheduled onto same node","user":{"login":"dshulyak","id":1964576,"avatar_url":"https://avatars.githubusercontent.com/u/1964576?v=3","gravatar_id":"","url":"https://api.github.com/users/dshulyak","html_url":"https://github.com/dshulyak","followers_url":"https://api.github.com/users/dshulyak/followers","following_url":"https://api.github.com/users/dshulyak/following{/other_user}","gists_url":"https://api.github.com/users/dshulyak/gists{/gist_id}","starred_url":"https://api.github.com/users/dshulyak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dshulyak/subscriptions","organizations_url":"https://api.github.com/users/dshulyak/orgs","repos_url":"https://api.github.com/users/dshulyak/repos","events_url":"https://api.github.com/users/dshulyak/events{/privacy}","received_events_url":"https://api.github.com/users/dshulyak/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/component/kubelet","name":"component/kubelet","color":"0052cc"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/control-plane","name":"team/control-plane","color":"d2b48c"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-08-31T12:11:14Z","updated_at":"2016-09-01T12:38:30Z","closed_at":null,"body":"\r\n**Kubernetes version** (use `kubectl version`):\r\nClient Version: version.Info{Major:\"1\", Minor:\"4+\", GitVersion:\"v1.4.0-alpha.2.1807+f80530c7f77e2f\", GitCommit:\"f80530c7f77e2fd272e6718b7d1754df0869d478\", GitTreeState:\"clean\", BuildDate:\"2016-08-29T12:08:57Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"4+\", GitVersion:\"v1.4.0-alpha.2.1807+f80530c7f77e2f\", GitCommit:\"f80530c7f77e2fd272e6718b7d1754df0869d478\", GitTreeState:\"clean\", BuildDate:\"2016-08-29T12:03:17Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n\r\n**Environment**:\r\n2 kubelet nodes + 1 master, deployed by local vagrant provider\r\n\r\n**What happened**:\r\nWhile working on https://github.com/kubernetes/kubernetes/issues/31098 I added `--eviction-hard=memory.available<90%` to evict pets from node-1. It did its job and they were evicted, but after that pod was constantly re-scheduled onto same node.\r\n\r\n**What you expected to happen**:\r\nExpected that eviction-hard will prevent pod from being scheduled onto the same node, as long as evict condition is preserved.\r\n\r\n**How to reproduce it** (as minimally and precisely as possible):\r\n1. Create petset (i was using cockroachdb example)\r\n2. Add `--eviction-hard=memory.available<90%` (or another condition which will evict pods from node)\r\n\r\nI didn't try it with regular pods, so you may need to use my patch https://github.com/kubernetes/kubernetes/pull/31777\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/244065710","html_url":"https://github.com/kubernetes/kubernetes/issues/31778#issuecomment-244065710","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/31778","id":244065710,"user":{"login":"derekwaynecarr","id":6233452,"avatar_url":"https://avatars.githubusercontent.com/u/6233452?v=3","gravatar_id":"","url":"https://api.github.com/users/derekwaynecarr","html_url":"https://github.com/derekwaynecarr","followers_url":"https://api.github.com/users/derekwaynecarr/followers","following_url":"https://api.github.com/users/derekwaynecarr/following{/other_user}","gists_url":"https://api.github.com/users/derekwaynecarr/gists{/gist_id}","starred_url":"https://api.github.com/users/derekwaynecarr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/derekwaynecarr/subscriptions","organizations_url":"https://api.github.com/users/derekwaynecarr/orgs","repos_url":"https://api.github.com/users/derekwaynecarr/repos","events_url":"https://api.github.com/users/derekwaynecarr/events{/privacy}","received_events_url":"https://api.github.com/users/derekwaynecarr/received_events","type":"User","site_admin":false},"created_at":"2016-09-01T12:38:30Z","updated_at":"2016-09-01T12:38:30Z","body":"For MemoryPressure, the Kubelet only rejects pods with BestEffort quality of service (ie pod that makes no memory or CPU request).  The same for scheduler.\r\n\r\nFor DiskPressure, Kubelet and scheduler will place no more pods on the node independent of QoS.\r\n\r\nCan you provide the YAML output for the pod that was scheduled on the node so we can see its resource requirements?"}}
{"actor":{"display_login":"derekwaynecarr"}}