{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubeadm/issues/697","repository_url":"https://api.github.com/repos/kubernetes/kubeadm","labels_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/697/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/697/comments","events_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/697/events","html_url":"https://github.com/kubernetes/kubeadm/issues/697","id":296151973,"number":697,"title":"KubeDNS should run as a daemonset","user":{"login":"HcgRandon","id":6123135,"avatar_url":"https://avatars1.githubusercontent.com/u/6123135?v=4","gravatar_id":"","url":"https://api.github.com/users/HcgRandon","html_url":"https://github.com/HcgRandon","followers_url":"https://api.github.com/users/HcgRandon/followers","following_url":"https://api.github.com/users/HcgRandon/following{/other_user}","gists_url":"https://api.github.com/users/HcgRandon/gists{/gist_id}","starred_url":"https://api.github.com/users/HcgRandon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/HcgRandon/subscriptions","organizations_url":"https://api.github.com/users/HcgRandon/orgs","repos_url":"https://api.github.com/users/HcgRandon/repos","events_url":"https://api.github.com/users/HcgRandon/events{/privacy}","received_events_url":"https://api.github.com/users/HcgRandon/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-11T02:00:27Z","updated_at":"2018-02-14T16:02:22Z","closed_at":null,"author_association":"NONE","body":"## What keywords did you search in kubeadm issues before filing this one?\r\ndns, kubedns, daemonset\r\n\r\n## Is this a BUG REPORT or FEATURE REQUEST?\r\nChoose one: FEATURE REQUEST\r\n\r\nDue to kube-dns running on only the master node in a `kubeadm init` cluster this creates a single point of failure for applications that heavily rely on dns, a simple reboot of the master node is enough to break such an application until master returns.\r\n\r\nFor these reasons I feel that kube-dns should run across all nodes in the cluster as a daemonset, or at least more then one node.\r\n\r\nThanks.\r\n\r\n## Versions\r\n\r\n**kubeadm version** (use `kubeadm version`):\r\n```\r\nroot@master-1:~# salt '*' cmd.run 'kubeadm version'\r\nus-east-1:\r\n    kubeadm version: &version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.3\", GitCommit:\"d2835416544f298c919e2ead3be3d0864b52323b\", GitTreeState:\"clean\", BuildDate:\"2018-02-07T11:55:20Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\nmaster-1:\r\n    kubeadm version: &version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.2\", GitCommit:\"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b\", GitTreeState:\"clean\", BuildDate:\"2018-01-18T09:42:01Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\neu-1:\r\n    kubeadm version: &version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.2\", GitCommit:\"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b\", GitTreeState:\"clean\", BuildDate:\"2018-01-18T09:42:01Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n```\r\n\r\n**Environment**:\r\n- **Kubernetes version** (use `kubectl version`):\r\n```\r\nClient Version: version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.2\", GitCommit:\"5fa2db2bd46ac79e5e00a4e6ed24191080aa463b\", GitTreeState:\"clean\", BuildDate:\"2018-01-18T10:09:24Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\nServer Version: version.Info{Major:\"1\", Minor:\"9\", GitVersion:\"v1.9.3\", GitCommit:\"d2835416544f298c919e2ead3be3d0864b52323b\", GitTreeState:\"clean\", BuildDate:\"2018-02-07T11:55:20Z\", GoVersion:\"go1.9.2\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n```\r\n- **Cloud provider or hardware configuration**:\r\nbare metal\r\n- **OS** (e.g. from /etc/os-release):\r\n```\r\nroot@master-1:~# salt '*' cmd.run 'cat /etc/os-release'\r\nmaster-1:\r\n    PRETTY_NAME=\"Debian GNU/Linux 8 (jessie)\"\r\n    NAME=\"Debian GNU/Linux\"\r\n    VERSION_ID=\"8\"\r\n    VERSION=\"8 (jessie)\"\r\n    ID=debian\r\n    HOME_URL=\"http://www.debian.org/\"\r\n    SUPPORT_URL=\"http://www.debian.org/support\"\r\n    BUG_REPORT_URL=\"https://bugs.debian.org/\"\r\nus-east-1:\r\n    PRETTY_NAME=\"Debian GNU/Linux 9 (stretch)\"\r\n    NAME=\"Debian GNU/Linux\"\r\n    VERSION_ID=\"9\"\r\n    VERSION=\"9 (stretch)\"\r\n    ID=debian\r\n    HOME_URL=\"https://www.debian.org/\"\r\n    SUPPORT_URL=\"https://www.debian.org/support\"\r\n    BUG_REPORT_URL=\"https://bugs.debian.org/\"\r\neu-1:\r\n    PRETTY_NAME=\"Debian GNU/Linux 9 (stretch)\"\r\n    NAME=\"Debian GNU/Linux\"\r\n    VERSION_ID=\"9\"\r\n    VERSION=\"9 (stretch)\"\r\n    ID=debian\r\n    HOME_URL=\"https://www.debian.org/\"\r\n    SUPPORT_URL=\"https://www.debian.org/support\"\r\n    BUG_REPORT_URL=\"https://bugs.debian.org/\"\r\n```\r\n- **Kernel** (e.g. `uname -a`):\r\n```\r\nroot@master-1:~# salt '*' cmd.run 'uname -a'\r\nmaster1:\r\n    Linux master-1 3.16.0-4-amd64 #1 SMP Debian 3.16.51-3 (2017-12-13) x86_64 GNU/Linux\r\nus-east-1:\r\n    Linux us-east-1 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux\r\neu-1:\r\n    Linux eu-1 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux\r\n```\r\n- **Others**:\r\n\r\n\r\n## What happened?\r\nOutbound traffic fails to continue, due to dns being unavailable for resolving ip\r\n\r\n## What you expected to happen?\r\ndns to continue to resolve without the presence of master, or at least dns lookups to fallback to current nodes /etc/resolve.conf\r\n\r\n## How to reproduce it (as minimally and precisely as possible)?\r\n1. init a kubeadm cluster\r\n2. create and deploy a simple application that does a lot of dns lookups to an external service (ie: example.com)\r\n3. reboot / turn off master node while application is running\r\n\r\n## Anything else we need to know?\r\nThe application where I am experiencing this behaviour is nodejs based.\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubeadm/issues/comments/365653754","html_url":"https://github.com/kubernetes/kubeadm/issues/697#issuecomment-365653754","issue_url":"https://api.github.com/repos/kubernetes/kubeadm/issues/697","id":365653754,"user":{"login":"webwurst","id":225698,"avatar_url":"https://avatars3.githubusercontent.com/u/225698?v=4","gravatar_id":"","url":"https://api.github.com/users/webwurst","html_url":"https://github.com/webwurst","followers_url":"https://api.github.com/users/webwurst/followers","following_url":"https://api.github.com/users/webwurst/following{/other_user}","gists_url":"https://api.github.com/users/webwurst/gists{/gist_id}","starred_url":"https://api.github.com/users/webwurst/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/webwurst/subscriptions","organizations_url":"https://api.github.com/users/webwurst/orgs","repos_url":"https://api.github.com/users/webwurst/repos","events_url":"https://api.github.com/users/webwurst/events{/privacy}","received_events_url":"https://api.github.com/users/webwurst/received_events","type":"User","site_admin":false},"created_at":"2018-02-14T16:02:22Z","updated_at":"2018-02-14T16:02:22Z","author_association":"NONE","body":"Maybe see https://github.com/kubernetes/kubernetes/pull/57683 and https://github.com/kubernetes/kubernetes/pull/59357 for some earlier discussion around this problem."}}
{"actor":{"display_login":"webwurst"}}