-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Umbrella: 1.11 kubeadm tracking issue #8846
Comments
/assign @Bradamant3 |
filtered list: https://github.com/kubernetes/kubeadm/issues?q=is%3Aissue+is%3Aopen+label%3Akind%2Fdocumentation FOR 1.11 ISSUE NAME: Create new documentation based on user stories ISSUE NAME: document "controlling kubelet Config via a versioned file" at website ISSUE NAME: Document source components for required ports for master and worker nodes ISSUE NAME: Example configs for using external Certificates ISSUE NAME: node-name different than ISSUE NAME: Concise outline for using cloud providers POST 1.11 ISSUE NAME: "document the process of bumping test-infra on each release" ISSUE NAME: Stale iptables rules seen after "kubeadm reset" ISSUE NAME: Self-hosted kubeadm clusters should still store the manifests somewhere... ISSUE NAME: Document all phases' high-level functions in ISSUE NAME: how can i specified external-etcd-endpoints in 1.8.0 ISSUE NAME: improve user experience about CNI errors ISSUE NAME: how to renewal apiserver.crt certificate,the default is one year |
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. |
/close |
@neolit123: 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. |
There are a bunch of documentation changes that are slated for 1.11 cycle and most are not major feature changes, however, we have not enumerated the entire list yet. This issue is meant to serve as the 1.11 kubeadm docs changes tracking issue. We intend to break down the entire docs list and those that need to hold till 1.11 release will reference this issue.
@kubernetes/sig-cluster-lifecycle-misc @neolit123 @luxas
The text was updated successfully, but these errors were encountered: