-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multicluster DNS #2577
Multicluster DNS #2577
Conversation
Hi @lauralorenz. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…rds in the readme
…ason to not need PTR records at multicluster DNS level
After talking to SIG-Network on 4/1 and confirming with SIG-Multicluster 4/13, we are keeping SRV records since use cases for it exist (VOIP, Active Directory, and etcd cluster bootstrapping being the concrete ones). I've added info about that and done a copyediting/formatting pass so I'm looking for official lgtms and approvals now. cc MCS API reviewer representing DNS @johnbelamaric and MCS API approvers @pmorie and @thockin |
/ok-to-test |
/retest |
/test pull-enhancements-verify |
/test pull-enhancements-verify |
Howdy @thockin, I finally incorporated all the SIG-Network feedback and besides nits, change highlights include
cc @prameshj and FYI @johnbelamaric I'm coming for your LGTM again next |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just nits!
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
keps/sig-multicluster/1645-multi-cluster-services-api/specification.md
Outdated
Show resolved
Hide resolved
Thanks! /lgtm |
Howdy @johnbelamaric your LGTM is needed again as it fell off when I made changes SIG-Network asked for. Changelog since you last LGTMd is
THANK YOU! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric, lauralorenz, thockin The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* adding skeleton for PR * move over everything except PTR records * Adding in PTR records * move <clustersetzone> being non configurable info to definition section, update links * update links again, more specific * add link to clusterid * Clean up prose flow a bit, and add some rationale on SRV and PTR records in the readme * in overview explicitly reference dummy service implementation as a reason to not need PTR records at multicluster DNS level * Copyediting and formatting * set initial schema version * getting a little picky about sticky caps on clusterset * fix toc * also add toc for specification.md * adding note on dual-stack * Change examples to use more readable clusterIDs and add in to headless SRV records for clarity * Be more clear about what hostname means in this spec file directly * allow flexibility on headless service DNS reporting a subset of pod IPs * clarify ClusterIPs are not necessarily accessible clusterset wide * fix zone->clustersetzone * reserve disallowed DNS forms for future use * for disallowed DNS records, they MUST NOT not just should not * use better prose for how ClusterSetIP DNS clusterips work * clustersetzone->clusterset-zone * S A V A G E removed PTR recordsgit status k bye * fix toc * fix toc again * add subset language to actual specification.md for headless service DNS * wording nits and follow RFC 1123 my own self * some formatting and clarify prose on subset used for headless A/AAAA records in dual stack case * rewrap specification.md * rewrap MCS API doc, praying the toc is healthy * toc did not like getting rewrapped yall
Moved in content from community doc proposals http://bit.ly/k8s-multicluster-dns and http://bit.ly/k8s-multicluster-dns-slides.
Notable changes here:
<clusterid>.<svc>.<ns>.svc.<clustersetzone>.
explicitly not allowed in the specification for either ClusterSetIP or Multicluster Headless Services with rationale explained in the KEP