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

1.14: docs updates #1422

Closed
3 tasks done
neolit123 opened this issue Feb 24, 2019 · 15 comments
Closed
3 tasks done

1.14: docs updates #1422

neolit123 opened this issue Feb 24, 2019 · 15 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/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented Feb 24, 2019

placeholder docs PRs for k/website should be sent until March 1st.
deadline for reviews is March 18th.

PRs should be sent against the k/website dev-1.14 branch.

marking this as help-wanted.


task: update kubeadm command line reference docs
assigned: @neolit123

info:
https://github.com/kubernetes/website/tree/master/content/en/docs/reference/setup-tools/kubeadm

  • we have new join phase commands.
  • need to look at what we kept or removed in other commands and flags.

task: add 1.13 -> 1.14 upgrade docs (single control-plane + HA)
assigned: @neolit123

info:
https://github.com/kubernetes/website/tree/master/content/en/docs/tasks/administer-cluster/kubeadm

add new page for 1.13->1.14 upgrade.
remove 1.10 -> 1.11 docs as well.


task: updates to HA docs in 1.14
assigned: @neolit123

info:
https://github.com/kubernetes/website/tree/master/content/en/docs/setup/independent
high-availability.md etc..

we are adding copy-certs support.

@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 Feb 24, 2019
@neolit123 neolit123 added this to the v1.14 milestone Feb 24, 2019
@neolit123 neolit123 self-assigned this Feb 24, 2019
@neolit123 neolit123 changed the title 1.14: updated reference docs 1.14: docs updates Feb 24, 2019
@neolit123 neolit123 added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Feb 24, 2019
@neolit123
Copy link
Member Author

@kubernetes/sig-cluster-lifecycle

i've added some tasks that need to be performed for updating the kubeadm 1.14 docs.

@RA489
Copy link
Contributor

RA489 commented Feb 25, 2019

@neolit123 I can help with this effort.

@neolit123
Copy link
Member Author

neolit123 commented Feb 27, 2019

@RA489 @Klaven
i've assigned you to a couple of items. see above and thank you very much.

let's post any questions in this thread instead of pinging on private, so that we can give the change of more people to respond.
thank you !

@yagonobre
Copy link
Member

I can take task: add 1.13 -> 1.14 upgrade docs (HA)

@neolit123
Copy link
Member Author

thanks @yagonobre !

@Klaven
Copy link

Klaven commented Feb 28, 2019

@neolit123 HA placeholder PR kubernetes/website#12892

@yagonobre
Copy link
Member

/assign

@neolit123
Copy link
Member Author

to modify existing branch of PR try this:
https://help.github.com/en/articles/changing-the-base-branch-of-a-pull-request

has to be dev-1.14.

@neolit123
Copy link
Member Author

^ or if this asks you to merge 100 commits just create a new PR.

@yagonobre
Copy link
Member

@neolit123 I created a new pr kubernetes/website#12913

@RA489
Copy link
Contributor

RA489 commented Mar 1, 2019

@neolit123 I created PR kubernetes/website#12919

@neolit123
Copy link
Member Author

thanks!

@Klaven
Copy link

Klaven commented Mar 1, 2019

@neolit123 I created a new PR! :D
kubernetes/website#12923

@neolit123 neolit123 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Mar 2, 2019
@neolit123 neolit123 added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 11, 2019
@yagonobre
Copy link
Member

/unassign

@jimangel
Copy link
Member

@neolit123 I think this is ok to close.

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/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

5 participants