-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Added IPv6 information to various Component documents #6535
Conversation
- support request - code bug report
Fix the not-working test case yaml for /doc/concepts/storage/volumes.md
Some edits for clarity and condensed language.
Fix format.
The url no need. just highlight.
Fix leading spaces in commands.
Fix format.
guarnatees to guarantees
* Added IPV6 information to setup cluster using kubeadm * Updated kubeadm.md & create-cluster-kubeadm.md with IPv6 related information * Added IPv6 options for kubeadm --init & automated address binding for kube-proxy based on version of IP configured for API server) * Changes to kubeadm.md as per comments * Modified kubeadm.md and create-cluster-kubeadm.md * Implemented changes requested by zacharysarah * Removed autogenerated kubeadm.md changes
* updates sts concept and tutorials to use 1.9 apps/v1 * Update statefulset.md * clarify pod name label
* 1.9 gc policy update * carify deletion
We also need to remove kubelet.md from this PR, because it is auto generated. See #6658. |
a74455e
to
ce79231
Compare
c4ea942
to
989acbf
Compare
|
Deploy preview ready! Built with commit 2849cf0 https://deploy-preview-6535--kubernetes-io-master-staging.netlify.com |
@mmueen Sorry for the delay. It looks like there's another merge conflict. If you can fix the conflict, I'll get this merged right away. Thanks. |
This PR needs to be rebased. The commit history is all muddled. Based on the changes mentioned in the description and issue, this PR should not touch anything except for Probably best to just create a clean fork off of |
@mmueen If you'd like to collaborate on getting the IPv6 changes into the upstream source for topics like kube-apiserver, you can get in touch with me in the sig-docs Slack channel. I have a PR in progress that discusses how generate reference docs: #6366. Preview of relevant topic. It looks to me like the upstream source for the kube-apiserver options is in files like serving.go. |
@steveperry-53 , sure yes I can help with that .. |
These changes are covered in the Kubernetes source code. |
What this PR does / why we need it:
Added IPv6 related information to following documents:
docs/concepts/configuration/overview.md
docs/reference/generated/kube-apiserver.md
docs/reference/generated/kube-controller-manager.md
docs/reference/generated/kube-scheduler.md
docs/reference/generated/kubeadm.md
docs/reference/generated/kubelet.md
Which issue(s) this PR addresses:
addresses kubernetes/kubernetes#53824
This change is