Skip to content
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 "CoreDNS by default in v1.11" #843

Closed
7 of 11 tasks
neolit123 opened this issue May 22, 2018 · 7 comments
Closed
7 of 11 tasks

document "CoreDNS by default in v1.11" #843

neolit123 opened this issue May 22, 2018 · 7 comments
Assignees
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented May 22, 2018

this PR set the feature gate for CoreDNS to true by default:
kubernetes/kubernetes#63509

feature discussion:
kubernetes/enhancements#427

document the transition in the docs (mentioned in a lot of places).

task list:

---> PR sent and amended multiple times.
kubernetes/website#8697

---> PR
kubernetes/website#8728

---> PR kubernetes/website#8727

---> PR
kubernetes/website#8753

discussion / proposal for changes:
https://docs.google.com/document/d/1RFAN8e0q_Zfyyz9ZYGB6m-vaArgAZsnrsbv8BaQdH8o/edit?usp=sharing

---> PR
kubernetes/website#8900

---> PR
kubernetes/website#8829

Kubernetes Features OSS tracking board (1.11 release):
https://docs.google.com/spreadsheets/d/16N9KSlxWwxUA2gV6jvuW9N8tPRHzNhu1-RYY4Y0RZLs/edit#gid=0


we are not touching the following DNS related pages:

if you think that we should do otherwise, do tell.

@neolit123 neolit123 added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels May 22, 2018
@neolit123 neolit123 added this to the v1.11 milestone May 22, 2018
@neolit123
Copy link
Member Author

i was instructed to break this into separate PRs against website, which will complicate things a bit.
@luxas, @timothysc, @detiber, i will bump this space when a new change is made so that you can quickly comment / approve to get the process going.

first one:
kubernetes/website#8697

@johnbelamaric
Copy link
Member

cc @rajansandeep

@rajansandeep
Copy link

@neolit123 Is it ok if I can help out with the documentation?

@neolit123
Copy link
Member Author

@rajansandeep that would be much appreciated. thank you.

can you please verify that the non-kubeadm links above need any updates?
we kind of searched for "dns" and ended up with that list.

@rajansandeep
Copy link

@neolit123 Sure. I'll check.
There will be a separate PR for each link?

@neolit123
Copy link
Member Author

@rajansandeep
so it was suggested to me to split them for easier review.

not necessarily separate PRs for all links, but perhaps we can create one for:
https://kubernetes.io/docs/tasks/administer-cluster/*
and one for:
https://kubernetes.io/docs/concepts/services-networking/*

@neolit123
Copy link
Member Author

neolit123 commented May 28, 2018

@rajansandeep

so the kubeadm related changes are mostly submitted as PRs now (list in first post).

i'm not sure you had a look at what has to be changed here:
https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/

i've created a google docs file to allow us to discuss this:
https://docs.google.com/document/d/1RFAN8e0q_Zfyyz9ZYGB6m-vaArgAZsnrsbv8BaQdH8o/edit?usp=sharing

please, have a look at my comments there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

5 participants