{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/37026","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/37026/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/37026/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/37026/events","html_url":"https://github.com/kubernetes/kubernetes/issues/37026","id":190162987,"number":37026,"title":"Service should favor local pods","user":{"login":"MartinPyka","id":8008840,"avatar_url":"https://avatars.githubusercontent.com/u/8008840?v=3","gravatar_id":"","url":"https://api.github.com/users/MartinPyka","html_url":"https://github.com/MartinPyka","followers_url":"https://api.github.com/users/MartinPyka/followers","following_url":"https://api.github.com/users/MartinPyka/following{/other_user}","gists_url":"https://api.github.com/users/MartinPyka/gists{/gist_id}","starred_url":"https://api.github.com/users/MartinPyka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MartinPyka/subscriptions","organizations_url":"https://api.github.com/users/MartinPyka/orgs","repos_url":"https://api.github.com/users/MartinPyka/repos","events_url":"https://api.github.com/users/MartinPyka/events{/privacy}","received_events_url":"https://api.github.com/users/MartinPyka/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-17T21:01:33Z","updated_at":"2016-11-17T21:01:33Z","closed_at":null,"body":"Working with Kubernetes 1.3.6\r\n\r\nThis is a feature request:\r\n\r\nit would be great if there would be any way to tell a service that an incoming request from a pod should be forwarded (if possible) to a pod that is located on the same node. This could save a lot of network traffic.\r\n\r\nExample\r\nNode1: worker-pod1, receiver-pod1\r\nNode2: worker-pod2\r\nNode3: worker-pod3, receiver-pod2\r\n\r\nreceiver-service load-balances receiver-pod1, receiver-pod2\r\n\r\nIf worker-pod1 sens a request to the receiver-service, its request should always end up on receiver-pod1, if available, because it is available on the same node. worker-pod2 gets redirected rr to either receiver-pod1 or receiver-pod2.\r\n\r\nUse cases in which network traffic could be saved: \r\n- sending logfiles to a local logstash instance\r\n- map/reduce-like scenarios\r\n- worker-nodes sending results to database clients\r\n\r\nBest,\r\nMartin"}}
{"actor":{"display_login":"MartinPyka"}}