{"action":"created","issue":{"url":"https://api.github.com/repos/aws/containers-roadmap/issues/221","repository_url":"https://api.github.com/repos/aws/containers-roadmap","labels_url":"https://api.github.com/repos/aws/containers-roadmap/issues/221/labels{/name}","comments_url":"https://api.github.com/repos/aws/containers-roadmap/issues/221/comments","events_url":"https://api.github.com/repos/aws/containers-roadmap/issues/221/events","html_url":"https://github.com/aws/containers-roadmap/issues/221","id":425220219,"node_id":"MDU6SXNzdWU0MjUyMjAyMTk=","number":221,"title":"DNS resolution for EKS Private Endpoints","user":{"login":"tabern","id":26726164,"node_id":"MDQ6VXNlcjI2NzI2MTY0","avatar_url":"https://avatars1.githubusercontent.com/u/26726164?v=4","gravatar_id":"","url":"https://api.github.com/users/tabern","html_url":"https://github.com/tabern","followers_url":"https://api.github.com/users/tabern/followers","following_url":"https://api.github.com/users/tabern/following{/other_user}","gists_url":"https://api.github.com/users/tabern/gists{/gist_id}","starred_url":"https://api.github.com/users/tabern/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tabern/subscriptions","organizations_url":"https://api.github.com/users/tabern/orgs","repos_url":"https://api.github.com/users/tabern/repos","events_url":"https://api.github.com/users/tabern/events{/privacy}","received_events_url":"https://api.github.com/users/tabern/received_events","type":"User","site_admin":false},"labels":[{"id":1143397512,"node_id":"MDU6TGFiZWwxMTQzMzk3NTEy","url":"https://api.github.com/repos/aws/containers-roadmap/labels/EKS","name":"EKS","color":"a8285d","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":25,"created_at":"2019-03-26T04:21:15Z","updated_at":"2019-06-24T20:15:09Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Automatic DNS resolution for EKS private endpoint private hosted zone within VPC. This allows fully direct connect functionality from on-prem computers to Kubernetes cluster API server that is only accessible within a VPC.\r\n\r\nFollow-up feature from https://github.com/aws/containers-roadmap/issues/22"},"comment":{"url":"https://api.github.com/repos/aws/containers-roadmap/issues/comments/505162343","html_url":"https://github.com/aws/containers-roadmap/issues/221#issuecomment-505162343","issue_url":"https://api.github.com/repos/aws/containers-roadmap/issues/221","id":505162343,"node_id":"MDEyOklzc3VlQ29tbWVudDUwNTE2MjM0Mw==","user":{"login":"newlyregistered26","id":11265091,"node_id":"MDQ6VXNlcjExMjY1MDkx","avatar_url":"https://avatars0.githubusercontent.com/u/11265091?v=4","gravatar_id":"","url":"https://api.github.com/users/newlyregistered26","html_url":"https://github.com/newlyregistered26","followers_url":"https://api.github.com/users/newlyregistered26/followers","following_url":"https://api.github.com/users/newlyregistered26/following{/other_user}","gists_url":"https://api.github.com/users/newlyregistered26/gists{/gist_id}","starred_url":"https://api.github.com/users/newlyregistered26/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/newlyregistered26/subscriptions","organizations_url":"https://api.github.com/users/newlyregistered26/orgs","repos_url":"https://api.github.com/users/newlyregistered26/repos","events_url":"https://api.github.com/users/newlyregistered26/events{/privacy}","received_events_url":"https://api.github.com/users/newlyregistered26/received_events","type":"User","site_admin":false},"created_at":"2019-06-24T20:15:09Z","updated_at":"2019-06-24T20:15:09Z","author_association":"NONE","body":"We are experiencing this issue when trying to communicate between two VPCs which have EKS clusters in them. We have one cluster which has prometheus deployed in a \"services\" type VPC trying to scrape metrics other workload VPCs. What we've noticed is that the cluster names are not always in the same DNS namespace, ie y4.ap-southeast-2.eks.amazonaws.com and another in sk1.ap-southeast-2.eks.amazonaws.com so we can use a workaround using a custom DNS zone with the internal API hosts files within sk1..... and associate this with the prometheus cluster in y4..... We are however unable to understand how the cluster naming works, as one environment still shares the same namespace as the services SVC which is overlapping and as such we can't associate this. There is another Kubernetes property which allows you to override specific pod DNS entries as below https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/, however we are using Prometheus Operator pattern and as such this doesn't support custom pod specs. Keenly watching this issue for updates."}}
{"actor":{"display_login":"newlyregistered26"}}