{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/41943","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/41943/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/41943/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/41943/events","html_url":"https://github.com/kubernetes/kubernetes/issues/41943","id":209626019,"number":41943,"title":"GCE kube-up doesn't install kube-proxy on the master","user":{"login":"caseydavenport","id":1944093,"avatar_url":"https://avatars.githubusercontent.com/u/1944093?v=3","gravatar_id":"","url":"https://api.github.com/users/caseydavenport","html_url":"https://github.com/caseydavenport","followers_url":"https://api.github.com/users/caseydavenport/followers","following_url":"https://api.github.com/users/caseydavenport/following{/other_user}","gists_url":"https://api.github.com/users/caseydavenport/gists{/gist_id}","starred_url":"https://api.github.com/users/caseydavenport/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/caseydavenport/subscriptions","organizations_url":"https://api.github.com/users/caseydavenport/orgs","repos_url":"https://api.github.com/users/caseydavenport/repos","events_url":"https://api.github.com/users/caseydavenport/events{/privacy}","received_events_url":"https://api.github.com/users/caseydavenport/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-02-23T00:29:54Z","updated_at":"2017-02-23T16:24:29Z","closed_at":null,"body":"Using the standard `cluster/kube-up.sh` installation script on GCE, it looks like the kube-proxy is installed on every node but not on the master.\r\n\r\nThis is a problem because even though the master is marked as unschedulable, the DaemonSet controller will still run pods on the master node, and those Pods won't be able to communicate via Kubernetes Services. \r\n\r\nAnd example would be a DaemonSet which tries to talk to the k8s API, but fails on the master since the `kubernetes.default` Service ClusterIP is not programmed.  Similarly, Pods started on the master via a DaemonSet won't have DNS access."},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/282042189","html_url":"https://github.com/kubernetes/kubernetes/issues/41943#issuecomment-282042189","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/41943","id":282042189,"user":{"login":"whitlockjc","id":98899,"avatar_url":"https://avatars.githubusercontent.com/u/98899?v=3","gravatar_id":"","url":"https://api.github.com/users/whitlockjc","html_url":"https://github.com/whitlockjc","followers_url":"https://api.github.com/users/whitlockjc/followers","following_url":"https://api.github.com/users/whitlockjc/following{/other_user}","gists_url":"https://api.github.com/users/whitlockjc/gists{/gist_id}","starred_url":"https://api.github.com/users/whitlockjc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whitlockjc/subscriptions","organizations_url":"https://api.github.com/users/whitlockjc/orgs","repos_url":"https://api.github.com/users/whitlockjc/repos","events_url":"https://api.github.com/users/whitlockjc/events{/privacy}","received_events_url":"https://api.github.com/users/whitlockjc/received_events","type":"User","site_admin":false},"created_at":"2017-02-23T16:24:29Z","updated_at":"2017-02-23T16:24:29Z","body":"I realize this didn't address the `debian` nodes, I'll get that sorted shortly."}}
{"actor":{"display_login":"whitlockjc"}}