-
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
Generated kubeadm docs for 1.11 are inconsistently formatted during release cycle #8723
Comments
@Bradamant3 Was this addressed by #8617? If so, could you close this issue? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is a...
Problem:
kubeadm docs generated during the 1.11 release cycle by anyone other than @tengqm do not include the HTML formatting that was added for 1.10. This is because kubernetes-sigs/reference-docs#47 is not merged.
Proposed Solution:
Life with mismatched formatting until 1.11 release. sig-docs regenerates all generated docs per release. At release time, if the PR is merged we'll have pretty tables for everything. If it isn't merged, we'll have less pretty lists for everything. But the inconsistencies will be gone.
Page to Update:
includes for siblings of https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm/
(source at https://github.com/kubernetes/website/tree/master/content/en/docs/reference/setup-tools/kubeadm/generated)
The text was updated successfully, but these errors were encountered: