{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/527","repository_url":"https://api.github.com/repos/kubernetes-incubator/kube-aws","labels_url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/527/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/527/comments","events_url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/527/events","html_url":"https://github.com/kubernetes-incubator/kube-aws/issues/527","id":220837426,"number":527,"title":"Cluster with apiEndpoints set fails to come up","user":{"login":"c-knowles","id":3053013,"avatar_url":"https://avatars0.githubusercontent.com/u/3053013?v=3","gravatar_id":"","url":"https://api.github.com/users/c-knowles","html_url":"https://github.com/c-knowles","followers_url":"https://api.github.com/users/c-knowles/followers","following_url":"https://api.github.com/users/c-knowles/following{/other_user}","gists_url":"https://api.github.com/users/c-knowles/gists{/gist_id}","starred_url":"https://api.github.com/users/c-knowles/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/c-knowles/subscriptions","organizations_url":"https://api.github.com/users/c-knowles/orgs","repos_url":"https://api.github.com/users/c-knowles/repos","events_url":"https://api.github.com/users/c-knowles/events{/privacy}","received_events_url":"https://api.github.com/users/c-knowles/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-04-11T04:36:32Z","updated_at":"2017-04-12T02:27:37Z","closed_at":null,"body":"Bringing up a new cluster up on latest master ae4956992dcea09a3b6f0973a2822f4875d1859c does not seem to work for config with `apiEndpoints` from https://github.com/kubernetes-incubator/kube-aws/pull/468, the workers fail to join the cluster.\r\n\r\nWith this config all works fine as before and the cluster comes up:\r\n\r\n```\r\nexternalDNSName: k8s-dev-v1.REDACTED\r\ncreateRecordSet: true\r\nrecordSetTTL: 60\r\n#hostedZone: \"\"\r\nhostedZoneId: REDACTED\r\n```\r\n\r\nBut switching to this config where everything else is identical the workers fail to become \"healthy\":\r\n\r\n```\r\n#externalDNSName: k8s-dev-v1.REDACTED\r\n#createRecordSet: true\r\n#recordSetTTL: 60\r\n#hostedZone: \"\"\r\n#hostedZoneId: REDACTED\r\n\r\napiEndpoints:\r\n  - name: versioned\r\n    createRecordSet: true\r\n    dnsName: k8s-dev-v1.REDACTED\r\n    hostedZone:\r\n      id: REDACTED\r\n    recordSetTTL: 60\r\n  - name: unversioned\r\n    dnsName: k8s-dev.REDACTED\r\n\r\nworker:\r\n  apiEndpointName: versioned\r\n```\r\n\r\nThe control plane stack ended up with resource `APIEndpointVersionedELB` and the update there update was complete pending cleanup. It was just the worker stack that failed to update.\r\n\r\nIn case anyone ends up here also, currently it seems impossible to `kube-aws update` a cluster when moving to `apiEndpoints` without updating the endpoints to a disjointed set. This is because CloudFormation tries to add a Route 53 RecordSet with the same value but different resource Logical ID. Workaround is to ensure endpoint DNS names do not contain existing `externalDNSName`."},"comment":{"url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/comments/293454346","html_url":"https://github.com/kubernetes-incubator/kube-aws/issues/527#issuecomment-293454346","issue_url":"https://api.github.com/repos/kubernetes-incubator/kube-aws/issues/527","id":293454346,"user":{"login":"mumoshu","id":22009,"avatar_url":"https://avatars3.githubusercontent.com/u/22009?v=3","gravatar_id":"","url":"https://api.github.com/users/mumoshu","html_url":"https://github.com/mumoshu","followers_url":"https://api.github.com/users/mumoshu/followers","following_url":"https://api.github.com/users/mumoshu/following{/other_user}","gists_url":"https://api.github.com/users/mumoshu/gists{/gist_id}","starred_url":"https://api.github.com/users/mumoshu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mumoshu/subscriptions","organizations_url":"https://api.github.com/users/mumoshu/orgs","repos_url":"https://api.github.com/users/mumoshu/repos","events_url":"https://api.github.com/users/mumoshu/events{/privacy}","received_events_url":"https://api.github.com/users/mumoshu/received_events","type":"User","site_admin":false},"created_at":"2017-04-12T02:27:37Z","updated_at":"2017-04-12T02:27:37Z","body":"@c-knowles Thanks for the report.\r\nIt definitely seems like my tests were not sufficient and a terrible bug that the various refs throughout kubeconfig and cloud-config-worker become empty when there're 2 or more API endpoints defined in cluster.yaml.\r\nI've already finished the fix in my local branch and I'll update the master branch shortly after more careful testings."}}
{"actor":{"display_login":"mumoshu"}}