{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kops/issues/3801","repository_url":"https://api.github.com/repos/kubernetes/kops","labels_url":"https://api.github.com/repos/kubernetes/kops/issues/3801/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kops/issues/3801/comments","events_url":"https://api.github.com/repos/kubernetes/kops/issues/3801/events","html_url":"https://github.com/kubernetes/kops/issues/3801","id":272272252,"number":3801,"title":"Ability to tweak DHCP Options sets in AWS","user":{"login":"iostat","id":2927187,"avatar_url":"https://avatars2.githubusercontent.com/u/2927187?v=4","gravatar_id":"","url":"https://api.github.com/users/iostat","html_url":"https://github.com/iostat","followers_url":"https://api.github.com/users/iostat/followers","following_url":"https://api.github.com/users/iostat/following{/other_user}","gists_url":"https://api.github.com/users/iostat/gists{/gist_id}","starred_url":"https://api.github.com/users/iostat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iostat/subscriptions","organizations_url":"https://api.github.com/users/iostat/orgs","repos_url":"https://api.github.com/users/iostat/repos","events_url":"https://api.github.com/users/iostat/events{/privacy}","received_events_url":"https://api.github.com/users/iostat/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-11-08T16:55:56Z","updated_at":"2018-02-07T18:34:40Z","closed_at":null,"author_association":"NONE","body":"Hi all!\r\n\r\nWe're running a cluster in AWS, and within that cluster we have an internal docker registry which serves most of the containers we use. We use the cluster-internal DNS to reference containers (i.e., `docker.ns.svc.cluster.local/foo/bar:baz`)  It almost works out of the box, except that we manually have to modify the DHCP options set for the VPC that Kops created so that it adds the `kube-dns` service's cluster IP address as a DNS server, in addition to `AmazonProvidedDNS`. (Otherwise, the docker instance on the hosts can't resolve the registry.) And of course, every time we run `kops update cluster`, it wants to change the DHCP options set back to the one it created when we spun up the cluster, which means we have to be a little careful around doing changes to the cluster spec to avoid newly spawned nodes being unable to resolve the registry (as they wouldn't be aware of `kube-dns` as a DNS server to resolve `.svc.cluster.local` addresses). \r\n\r\nIt'd be great if there was a way to either specify `extraDNSServers` somewhere in the cluster spec or even just to simply disable the VPC DHCP Options check when running `kops update cluster`\r\n\r\nCheers!"},"comment":{"url":"https://api.github.com/repos/kubernetes/kops/issues/comments/363865987","html_url":"https://github.com/kubernetes/kops/issues/3801#issuecomment-363865987","issue_url":"https://api.github.com/repos/kubernetes/kops/issues/3801","id":363865987,"user":{"login":"fejta-bot","id":30488982,"avatar_url":"https://avatars1.githubusercontent.com/u/30488982?v=4","gravatar_id":"","url":"https://api.github.com/users/fejta-bot","html_url":"https://github.com/fejta-bot","followers_url":"https://api.github.com/users/fejta-bot/followers","following_url":"https://api.github.com/users/fejta-bot/following{/other_user}","gists_url":"https://api.github.com/users/fejta-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/fejta-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fejta-bot/subscriptions","organizations_url":"https://api.github.com/users/fejta-bot/orgs","repos_url":"https://api.github.com/users/fejta-bot/repos","events_url":"https://api.github.com/users/fejta-bot/events{/privacy}","received_events_url":"https://api.github.com/users/fejta-bot/received_events","type":"User","site_admin":false},"created_at":"2018-02-07T18:34:40Z","updated_at":"2018-02-07T18:34:40Z","author_association":"NONE","body":"Issues go stale after 90d of inactivity.\nMark the issue as fresh with `/remove-lifecycle stale`.\nStale issues rot after an additional 30d of inactivity and eventually close.\n\nIf this issue is safe to close now please do so with `/close`.\n\nSend feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta).\n/lifecycle stale"}}
{"actor":{"display_login":"fejta-bot"}}