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

taints/tolerations documentation for 1.6 #2737

Closed
2 tasks
gyliu513 opened this issue Mar 8, 2017 · 9 comments
Closed
2 tasks

taints/tolerations documentation for 1.6 #2737

gyliu513 opened this issue Mar 8, 2017 · 9 comments
Assignees

Comments

@gyliu513
Copy link
Contributor

gyliu513 commented Mar 8, 2017

This is a...

  • Feature Request
  • Bug Report

Problem:
Please refer to https://groups.google.com/forum/#!search/taints$2Ftolerations$20documentation$20effort$20for$201.6/kubernetes-sig-scheduling/MFt4zjtaRuI/NrOOaSULEgAJ for detail.

Proposed Solution:

Page to Update:
http://kubernetes.io/...

@gyliu513
Copy link
Contributor Author

/assign @gyliu513

@ravisantoshgudimetla
Copy link
Contributor

@gyliu513 I'd recommend to add milestone 1.6 to these PR's. It seems 03/17 is last date for documentation changes.

@gyliu513
Copy link
Contributor Author

Seems I donot have permission to add labels for those PRs, can you please help @ravisantoshgudimetla

@ravisantoshgudimetla
Copy link
Contributor

@gyliu513 I don't have either.

/cc @aveshagarwal @timothysc @davidopp

@gyliu513
Copy link
Contributor Author

gyliu513 commented Mar 18, 2017

/cc @kubernetes/sig-docs-maintainers I think that this needs to catch 1.6 release, can anyone help? Thanks!

@davidopp
Copy link
Member

I found out that it is possible to change the branch after the PR is created (go to "edit" in the PR on Github, and change the base branch). So, I have modified your PRs to now point to the release-1.6 branch.

@gyliu513
Copy link
Contributor Author

@aveshagarwal @davidopp shall we close this issue?

@gyliu513
Copy link
Contributor Author

@davidopp @aveshagarwal do you know when we need to merge this to master branch or it will be merged automatically?

@davidopp
Copy link
Member

Yes the docs team will take care of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants