Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
dns-custom-namerserver: break down the page into mutliple sections #8900
Deploy preview for kubernetes-io-vnext-staging processing.
Built with commit 39c799f
Jun 4, 2018
I see nothing technically incorrect here. Although, organizationally, this information is presented as "How to configure CoreDNS" ... and it only covers the kube-dns equivalent functionality (stubdomains, nameservers, federation). More precisely, it shows examples of those options in kube-dns, and how they can be defined in CoreDNS.
A true "How to configure CoreDNS" would be much more extensive, also covering various use cases that kube-dns cannot handle. So I'd suggest we re-introduce this CoreDNS section as a "Moving from kube-dns to CoreDNS" configuration migration section.
@Bradamant3 i think this is fine, as is.
@johnbelamaric much appreciated.
all, i think we should make a 30 minute Zoom meeting outside of regular SIG meetings, possibly after the 1.11 docs freeze, invite SIG-cluster-lifecycle, SIG-docs and SIG-networking representatives and discuss all the DNS related topics - possibly reduce the amount of sparse information.
@johnbelamaric wdyt of holding off on reorg until after 1.11 release? I spent a lot of time copyediting the current structure bc I didn't have bandwidth to think through the kind of work you propose, and I don't have time to provide that kind of feedback again in the 1.11 timeline. But the work you propose is exactly what this page needs, I agree.
Also agree with @neolit123 's idea to meet separately about DNS related topics. It's great to have y'all so involved in helping clean up docs properly, but we need to coordinate timing of efforts better. At the end of the release cycle works for dev, but not for docs. So reorg work, for example, is probably best planned iteratively against master, so that we can merge and publish those commits throughout the release cycle.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Bradamant3
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