-
Notifications
You must be signed in to change notification settings - Fork 14.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
Document Federation CoreDNS support. #2197
Comments
Do you have further ideas of how this would fit into existing content? Need any guidance from the docs team? |
I would give it a try and come up with a draft in couple of days. any pointers that would help me in this task would be great and thanks for help offer. |
Sure, I'd suggest starting with the page template for tasks: https://kubernetes.io/docs/contribute/page-templates/ Do you know where you're going to put the page on the site? |
the federation deployment using CoreDNS would mostly be associated with this page https://kubernetes.io/docs/admin/federation/kubefed/ |
@jaredbhatti this doc will probably be one of the user guides. I am not entirely sure under what sub-heading, but it should go somewhere there and should be easily discoverable from other federation docs such as the kubefed doc that @shashidharatd linked. |
kubernetes/kubernetes#40536 is the umbrella issue for tracking this and others targeting improvements in non-cloud deployment of the federation control plane. |
I am currently facing the issue mentioned in http://stackoverflow.com/questions/43759332/coredns-in-k8s-federation-in-on-prem-clusters-doesnt-work. I would appreciate if someone could tell me the reason of this behavior or possible fixes of this problem. I have followed all the steps mentioned in the documentation. |
Have you asked the kubernetes-dev group (https://groups.google.com/forum/#!forum/kubernetes-dev)? |
It is not entirely clear how to use CoreDNS as a DNS provider for federation. We need a doc walking through the setup.
cc @kubernetes/sig-federation-misc
The text was updated successfully, but these errors were encountered: