{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/contrib/issues/2886","repository_url":"https://api.github.com/repos/kubernetes/contrib","labels_url":"https://api.github.com/repos/kubernetes/contrib/issues/2886/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/contrib/issues/2886/comments","events_url":"https://api.github.com/repos/kubernetes/contrib/issues/2886/events","html_url":"https://github.com/kubernetes/contrib/issues/2886","id":313989829,"number":2886,"title":"Kubernetes features - deciding which pod runs on which worker","user":{"login":"abhaynayak24","id":18603778,"avatar_url":"https://avatars1.githubusercontent.com/u/18603778?v=4","gravatar_id":"","url":"https://api.github.com/users/abhaynayak24","html_url":"https://github.com/abhaynayak24","followers_url":"https://api.github.com/users/abhaynayak24/followers","following_url":"https://api.github.com/users/abhaynayak24/following{/other_user}","gists_url":"https://api.github.com/users/abhaynayak24/gists{/gist_id}","starred_url":"https://api.github.com/users/abhaynayak24/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abhaynayak24/subscriptions","organizations_url":"https://api.github.com/users/abhaynayak24/orgs","repos_url":"https://api.github.com/users/abhaynayak24/repos","events_url":"https://api.github.com/users/abhaynayak24/events{/privacy}","received_events_url":"https://api.github.com/users/abhaynayak24/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-04-13T06:59:03Z","updated_at":"2018-04-13T08:01:00Z","closed_at":null,"author_association":"NONE","body":"Hi,\r\n\r\nI'm exploring kubernetes and I see that when the pod is created, the master automatically assigns it to some worker (I'm guessing randomly) in the cluster.\r\n\r\nHowever, if the worker1 (low CPU specs) gets overloaded it extends the pod to worker2 (high-end CPU specs) eventually. I know that every time the pod will be overloaded and shifted to this high-end worker but still the master always initializes the pod on worker1.\r\n\r\nIs there any feature which can allow me to configure the master such that it deploys the pods directly on the high-end worker rather than deploying it on a weak system and then shifting on to a better one? "},"comment":{"url":"https://api.github.com/repos/kubernetes/contrib/issues/comments/381056700","html_url":"https://github.com/kubernetes/contrib/issues/2886#issuecomment-381056700","issue_url":"https://api.github.com/repos/kubernetes/contrib/issues/2886","id":381056700,"user":{"login":"abhaynayak24","id":18603778,"avatar_url":"https://avatars1.githubusercontent.com/u/18603778?v=4","gravatar_id":"","url":"https://api.github.com/users/abhaynayak24","html_url":"https://github.com/abhaynayak24","followers_url":"https://api.github.com/users/abhaynayak24/followers","following_url":"https://api.github.com/users/abhaynayak24/following{/other_user}","gists_url":"https://api.github.com/users/abhaynayak24/gists{/gist_id}","starred_url":"https://api.github.com/users/abhaynayak24/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abhaynayak24/subscriptions","organizations_url":"https://api.github.com/users/abhaynayak24/orgs","repos_url":"https://api.github.com/users/abhaynayak24/repos","events_url":"https://api.github.com/users/abhaynayak24/events{/privacy}","received_events_url":"https://api.github.com/users/abhaynayak24/received_events","type":"User","site_admin":false},"created_at":"2018-04-13T08:00:59Z","updated_at":"2018-04-13T08:00:59Z","author_association":"NONE","body":"@champsaurav my thought process is something like this\r\nIf I can get the CPU usage/Memory usage of all the workers, then I can choose on which node should the pod be deployed according to the pods load.\r\n\r\nthe other option that I've is to create a database where in I've the final state of pods (which worker the pod runs at maximum load). From this database I can learn and next time when the pod is initialized I can make the master deploy the pod on the final worker directly"}}
{"actor":{"display_login":"abhaynayak24"}}