Add kubeadm upgrade docs for 1.11 #9089
Conversation
k8s-ci-robot
added
cncf-cla: yes
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit e6d2608 https://deploy-preview-9089--kubernetes-io-master-staging.netlify.com |
1 similar comment
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit e6d2608 https://deploy-preview-9089--kubernetes-io-master-staging.netlify.com |
|
@liztio please rebase against the 1.11 branch /hold |
k8s-ci-robot
added
the
do-not-merge/hold
k8s-ci-robot
added
size/XXL
liztio
force-pushed
the
kubeadm-111-upgrade
branch
from
e6d2608 to
7fa22ab
Compare
|
Deploy preview for kubernetes-io-vnext-staging processing. Built with commit 7fa22ab https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5b23f1a5b13fb110c64baa80 |
k8s-ci-robot
added
size/L
|
Deploy preview for kubernetes-io-vnext-staging processing. Built with commit 68bcbc2 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5b31344b02ed835439088897 |
|
@Bradamant3 done |
|
/cc @kubernetes/sig-cluster-lifecycle-pr-reviews |
k8s-ci-robot
added
the
sig/cluster-lifecycle
| @@ -0,0 +1,303 @@ | |||
| --- | |||
| reviewers: | |||
| - pipejakob | |||
There was a problem hiding this comment.
nix all these and use the alias
- sig-cluster-lifecycle
There was a problem hiding this comment.
I really should get #8506 in after all the docs flux of the release
| Before proceeding: | ||
|
|
||
| - You need to have a functional `kubeadm` Kubernetes cluster running version 1.10.0 or higher in order to use the process described here. Swap also needs to be disabled. | ||
| - Make sure you read the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.9.md) carefully. |
|
|
||
| - You need to have a functional `kubeadm` Kubernetes cluster running version 1.10.0 or higher in order to use the process described here. Swap also needs to be disabled. | ||
| - Make sure you read the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.9.md) carefully. | ||
| - `kubeadm upgrade` now allows you to upgrade etcd. `kubeadm upgrade` will also upgrade of etcd to 3.1.10 as part of upgrading from v1.8 to v1.9 by default. This is due to the fact that etcd 3.1.10 is the officially validated etcd version for Kubernetes v1.9. The upgrade is handled automatically by kubeadm for you. |
There was a problem hiding this comment.
nix this whole statement, not needed and not correct.
There was a problem hiding this comment.
Shouldn't we at least say kubeadm will upgrade your etcd if it's hosted locally and --etcd-upgrade is true?
There was a problem hiding this comment.
I don't think we really need to mention this since we will show this in the plan output.
| 1. Install the most recent version of `kubeadm` using `curl` like so: | ||
|
|
||
| ```shell | ||
| sudo apt-get upgdate && sudo apt-get upgrade kubeadm |
There was a problem hiding this comment.
You need to use curl here. Otherwise the kubeadm deb will pull in the new dropin and restart the old kubelet 😱.
Part of why I did the kubelet config refactor was to remove this curl need and be able to install kubeadm via apt/yum, curl won't be needed next time
There was a problem hiding this comment.
@luxas I tested this myself, it works just fine on Ubuntu xenial?
There was a problem hiding this comment.
@lizto I haven't tested specifically for the v1.11 upgrades, but with previous versions installing the kubeadm deb caused a service restart of the kubelet.
There was a problem hiding this comment.
https://asciinema.org/a/PEvquZxQzHpjJWh1dRUfcBCIE proof is in the pudding
There was a problem hiding this comment.
After speaking with @liztio about this yesterday we discovered that part of the diff between the kubeadm packages built using bazel from k/k and the release tooling is the postinstall kubelet restart 😢
There was a problem hiding this comment.
@detiber yes, hence my comment. We should fix the bazel packages. Can any of you open an issue about that?
| <!-- TODO: copy-paste actual output once new version is stable --> | ||
|
|
||
| ```shell | ||
| [preflight] Running pre-flight checks |
There was a problem hiding this comment.
This whole section needs to match v1.11 text.
|
|
||
| {{% capture overview %}} | ||
|
|
||
| This guide is for upgrading `kubeadm` clusters from version 1.10.x to 1.11.x, as well as 1.10.x to 1.10.y and 1.11.x to 1.11.y where `y > x`. |
There was a problem hiding this comment.
We removed the possibility for kubeadm v1.11.0 to upgrade from v1.10.3 to v1.10.4 right b/c of the config stuff right?
Then this should be changed accordingly
| 1. Install the most recent version of `kubeadm` using `curl` like so: | ||
|
|
||
| ```shell | ||
| sudo apt-get upgdate && sudo apt-get upgrade kubeadm |
There was a problem hiding this comment.
You need to use curl here. Otherwise the kubeadm deb will pull in the new dropin and restart the old kubelet 😱.
Part of why I did the kubelet config refactor was to remove this curl need and be able to install kubeadm via apt/yum, curl won't be needed next time
|
|
||
| You should see output similar to this: | ||
|
|
||
| <!-- TODO: copy-paste actual output once new version is stable --> |
There was a problem hiding this comment.
Now it should kinda be from master
There was a problem hiding this comment.
What do you mean by this?
There was a problem hiding this comment.
You can now paste the "right" output from master/the release candidate and it's gonna be correct, no need to wait anymore
There was a problem hiding this comment.
Everything is still suffixed with upgrading to version -beta.2.78+<hash>, so I still want to wait.
| [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. | ||
| ``` | ||
|
|
||
| To upgrade the cluster with CoreDNS as the default internal DNS, invoke `kubeadm upgrade apply` with the `--feature-gates=CoreDNS=true` flag. |
There was a problem hiding this comment.
Say that now CoreDNS is default, and tell the user if they don't wanna switch do X, Y and Z
There was a problem hiding this comment.
It should probably be called out at the top, and this section should probably be updated to show how to keep kube-dns rather than coredns.
| ``` | ||
|
|
||
| To upgrade the cluster with CoreDNS as the default internal DNS, invoke `kubeadm upgrade apply` with the `--feature-gates=CoreDNS=true` flag. | ||
| `kubeadm upgrade apply` does the following: |
There was a problem hiding this comment.
Move this to a reference, FYI section below?
| apt-get upgrade | ||
| ``` | ||
|
|
||
| If the host is running CentOS or the like, run: |
There was a problem hiding this comment.
Can you do tabs like the installing kubeadm page has for ubuntu/centos?
| @@ -0,0 +1,303 @@ | |||
| --- | |||
| reviewers: | |||
| - pipejakob | |||
There was a problem hiding this comment.
I really should get #8506 in after all the docs flux of the release
|
|
||
| - You need to have a functional `kubeadm` Kubernetes cluster running version 1.10.0 or higher in order to use the process described here. Swap also needs to be disabled. | ||
| - Make sure you read the [release notes](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.9.md) carefully. | ||
| - `kubeadm upgrade` now allows you to upgrade etcd. `kubeadm upgrade` will also upgrade of etcd to 3.1.10 as part of upgrading from v1.8 to v1.9 by default. This is due to the fact that etcd 3.1.10 is the officially validated etcd version for Kubernetes v1.9. The upgrade is handled automatically by kubeadm for you. |
There was a problem hiding this comment.
Shouldn't we at least say kubeadm will upgrade your etcd if it's hosted locally and --etcd-upgrade is true?
| - Makes sure the control plane images are available or available to pull to the machine. | ||
| - Upgrades the control plane components or rollbacks if any of them fails to come up. | ||
| - Applies the new `kube-dns` and `kube-proxy` manifests and enforces that all necessary RBAC rules are created. | ||
| - Creates new certificate and key files of apiserver and backs up old files if they're about to expire in 180 days. |
There was a problem hiding this comment.
should we apiserver -> the API server here?
| ``` | ||
|
|
||
| `kubeadm` is only needed on individual (non-master) nodes for joining the cluster. | ||
| It is not necessary to update kubeadm on nodes |
There was a problem hiding this comment.
These statements read a bit awkward and can probably just be removed, since this section is about updating the control plane and does not talk about taking actions on nodes.
There was a problem hiding this comment.
I found this confusing while I was working on this, so I think it's worth including. Open to wording suggestions
There was a problem hiding this comment.
Actually, going back to think about this, since we rely on the updated systemd drop-in file, we may actually require an updated kubeadm package on the worker nodes 😭
There was a problem hiding this comment.
Also this is false with v1.11, that requires the user to do kubeadm upgrade node config right before apt-get upgrade on nodes.
|
|
||
| {{% capture prerequisites %}} | ||
|
|
||
| Before proceeding: |
There was a problem hiding this comment.
we should talk about what kind of setup we are covering here. It's not enough to say a kubeadm k8s cluster. kubeadm allows many configurations and we only support some of the combinations.
For example we will not be supporting upgrades for clusters using an external etcd
There was a problem hiding this comment.
We should definitely fix upgrading external etcd in a patch release of v1.11 IMO
|
|
||
| 1. Install the most recent version of `kubeadm` using `curl` like so: | ||
|
|
||
| ```shell |
There was a problem hiding this comment.
this whole section under the numbered list will have to be indented 4 or 5 spaces (i have seen both /shrug) to preserve the correct numbering on the numbered list. The preview shows all the numbered items as "1" https://deploy-preview-9089--kubernetes-io-master-staging.netlify.com/docs/tasks/administer-cluster/upgrade-downgrade/kubeadm-upgrade-1-11/
mdlinville
force-pushed
the
kubeadm-111-upgrade
branch
from
7fa22ab to
e3663c5
Compare
|
I haven't tested the kube-dns upgrade stuff very thoroughly (couldn't get it to boot properly) and the markdown was copied from the old docs, so it's not quite hugo-ified properly. |
|
|
||
|
|
||
| `kubeadm` is only needed on individual (non-master) nodes for joining the cluster. | ||
| It is not necessary to update kubeadm on nodes |
There was a problem hiding this comment.
I believe that @luxas mentioned that it is required for the worker nodes during a v1.10.x -> v1.11.x upgrade to migrate to the kubelet component config.
There was a problem hiding this comment.
Yes there will be a step to grab the config on the upgrade command that requires the latest version.
| [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. | ||
| ``` | ||
|
|
||
| To upgrade the cluster with CoreDNS as the default internal DNS, invoke `kubeadm upgrade apply` with the `--feature-gates=CoreDNS=true` flag. |
There was a problem hiding this comment.
This line shouldn't be needed anymore as this is the current default.
| {{% /tab %}} | ||
| {{< /tabs >}} | ||
|
|
||
| Upgrading `kubeadm` is only required on the master node. |
There was a problem hiding this comment.
I believe this is not the case for v1.11, since we need to migrate to the component config.
There was a problem hiding this comment.
ah right, new I forgot something. I haven't had a chance to test this, what's the command?
There was a problem hiding this comment.
what does the upgrade command do, anyway? migrate the environment files?
There was a problem hiding this comment.
I haven't actually run through it myself yet, but it looks like it is kubeadm upgrade node config
There was a problem hiding this comment.
It appears to just download the config map and download it to the location configured in the updated systemd drop-in file.
|
|
||
| Before proceeding: | ||
|
|
||
| - You need to have a functional `kubeadm` Kubernetes cluster running version 1.10.0 or higher in order to use the process described here. Swap also needs to be disabled. This cluster should use a self-hosted etcd and static control plane pods. |
There was a problem hiding this comment.
'self hosted etcd' ?
It's all static pods.
| [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. | ||
| ``` | ||
|
|
||
| To upgrade the cluster with CoreDNS as the default internal DNS, invoke `kubeadm upgrade apply` with the `--feature-gates=CoreDNS=true` flag. |
There was a problem hiding this comment.
agreed this should be removed.
|
|
||
|
|
||
| `kubeadm` is only needed on individual (non-master) nodes for joining the cluster. | ||
| It is not necessary to update kubeadm on nodes |
There was a problem hiding this comment.
Yes there will be a step to grab the config on the upgrade command that requires the latest version.
| **Caution:** Upgrading the `kubeadm` package on your system prior to upgrading the control plane causes a failed upgrade. | ||
| Even though `kubeadm` ships in the Kubernetes repositories, it's important to install `kubeadm` manually. The kubeadm | ||
| team is working on fixing this limitation. | ||
| {{< /caution >}} |
There was a problem hiding this comment.
It looks like this caution is repeated.
There was a problem hiding this comment.
whoops! overzealous ediffing 😅
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
@Bradamant3 - good to go here. |
k8s-ci-robot
removed
the
lgtm
|
@liztio one question inline. Note that I had to add some headings to hack around newly discovered issues with list continuation in Blackfriday markdown. Specifically, it looks as though you can't put a tabset inside a listitem if there are following items in the same list. Or if you can, I didn't have time to figure out the trick. Indentation and code fences continue to behave unpredictably inside listitems also. Normalized for the most part, but clean output was my main criterion, so there may be what look like some inconsistencies in the markdown itself. |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bradamant3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
/hold cancel 🎉 🎉 🎉 |
k8s-ci-robot
removed
the
do-not-merge/hold
* Add kubeadm upgrade docs for 1.11 * Initial docs review feedback * Add 1-11 to outline * Fix formatting on tab blocks * Move file to correct location * Add `kubeadm upgrade node config` step * Overzealous ediffing * copyedit, fix lists and headings * clarify --force flag for fixing bad state
* Add kubeadm upgrade docs for 1.11 * Initial docs review feedback * Add 1-11 to outline * Fix formatting on tab blocks * Move file to correct location * Add `kubeadm upgrade node config` step * Overzealous ediffing * copyedit, fix lists and headings * clarify --force flag for fixing bad state
* Seperate priority and preemption (#8144) * Doc about PID pressure condition. (#8211) * Doc about PID pressure condition. Signed-off-by: Da K. Ma <[email protected]> * "so" -> "too" * Update version selector for 1.11 * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * CRIContainerLogRotation is Beta in 1.11 (#8665) * Seperate priority and preemption (#8144) * CRIContainerLogRotation is Beta in 1.11 xref: kubernetes/kubernetes#64046 * Bring StorageObjectInUseProtection feature to GA (#8159) * StorageObjectInUseProtection is GA (#8291) * Feature gate: StorageObjectInUseProtection is GA Update feature gate reference for 1.11 * Trivial commit to re-trigger Netlify * Bring StorageObjectInUseProtection feature to GA StorageObjectInUseProtection is Beta in K8s 1.10. It's brought to GA in K8s 1.11. * Fixed typo and added feature state tags. * Remove KUBE_API_VERSIONS doc (#8292) The support to the KUBER_API_VERSIONS environment variable is completely dropped (no deprecation). This PR removes the related doc in release-1.11. xref: kubernetes/kubernetes#63165 * Remove InitialResources from admission controllers (#8293) The feature (was experimental) is dropped in 1.11. xref: kubernetes/kubernetes#58784 * Remove docs related to in-tree support to GPU (#8294) * Remove docs related to in-tree support to GPU The in-tree support to GPU is completely removed in release 1.11. This PR removes the related docs in release-1.11 branch. xref: kubernetes/kubernetes#61498 * Update content updated by PR to Hugo syntax Signed-off-by: Misty Stanley-Jones <[email protected]> * Update the doc about extra volume in kubeadm config (#8453) Signed-off-by: Xianglin Gao <[email protected]> * Update CRD Subresources for 1.11 (#8519) * coredns: update notes in administer-cluster/coredns.md (#8697) CoreDNS is installed by default in 1.11. Add notes on how to install kube-dns instead. Update notes about CoreDNS->CoreDNS upgrades as in 1.11 the Corefile is retained. Add example on upgrading from kube-dns to CoreDNS. * kubeadm-alpha: CoreDNS related changes (#8727) Update note about CoreDNS feature gate. This change also updates a tab as a kubeadm sub-command will change. It looks for a new generated file: generated/kubeadm_alpha_phase_addon_coredns.md instead of: generated/kubeadm_alpha_phase_addon_kube-dns.md * Update cloud controller manager docs to beta 1.11 (#8756) * Update cloud controller manager docs to beta 1.11 * Use Hugo shortcode for feature state * kubeadm-upgrade: include new command `kubeadm upgrade diff` (#8617) Also: - Include note that this was added in 1.11. - Modify the note about upgrade guidance. * independent: update CoreDNS mentions for kubeadm (#8753) Give CoreDNS instead of kube-dns examples in: - docs/setup/independent/create-cluster-kubeadm.md - docs/setup/independent/troubleshooting-kubeadm.md * update 1.11 --server-print info (#8870) * update 1.11 --server-print info * Copyedit * Mark ExpandPersistentVolumes feature to beta (#8778) * Update version selector for 1.11 * Mark ExpandPersistentVolumes Beta xref: kubernetes/kubernetes#64288 * fix shortcode, add placeholder files to fix deploy failures (#8874) * declare ipvs ga (#8850) * kubeadm: update info about CoreDNS in kubeadm-init.md (#8728) Add info to install kube-dns instead of CoreDNS, as CoreDNS is the default DNS server in 1.11. Add notes that kubeadm config images can be used to list and pull the required images in 1.11. * kubeadm: update implementation-details.md about CoreDNS (#8829) - Replace examples from kube-dns to CoreDNS - Add notes about the CoreDNS feature gate status in 1.11 - Add note that the service name for CoreDNS is also called `kube-dns` * Update block device support for 1.11 (#8895) * Update block device support for 1.11 * Copyedits * Fix typo 'fiber channel' (#8957) Signed-off-by: Misty Stanley-Jones <[email protected]> * kubeadm-upgrade: add the 'node [config]' sub-command (#8960) - Add includes for the generated pages - Include placeholder generated pages * kubeadm-init: update the example for the MasterConfiguration (#8958) - include godocs link for MasterConfiguration - include example MasterConfiguration - add note that `kubeadm config print-default` can be used * kubeadm-config: include new commands (#8862) Add notes and includes for these new commands in 1.11: - kubeadm config print-default - kubeadm config migrate - kubeadm config images list - kubeadm config images pull Include placeholder generated files for the above. * administer-cluster/coredns: include more changes (#8985) It was requested that for this page a couple of methods should be outlined: - manual installation for CoreDNS explained at the Kubernetes section of the GitHub project for CoreDNS - installation and upgrade via kubeadm Make the above changes and also add a section "About CoreDNS". This commit also lowercases a section title. * Update CRD subresources doc for 1.11 (#8918) * Add docs for volume expansion and online resizing (#8896) * Add docs for volume expansion going beta * Copyedit * Address feedback * Update exec plugin docs with TLS credentials (#8826) * Update exec plugin docs with TLS credentials kubernetes/kubernetes#61803 implements TLS client credential support for 1.11. * Copyedit * More copyedits for clarification * Additional copyedit * Change token->credential * NodeRestriction admission prevents kubelet taint removal (#8911) * dns-custom-namerserver: break down the page into mutliple sections (#8900) * dns-custom-namerserver: break down the page into mutliple sections This page is currently about kube-dns and is a bit outdated. Introduce the heading `# Customizing kube-dns`. Introduce a separate section about CoreDNS. * Copyedits, fix headings for customizing DNS Hey Lubomir, I coypedited pretty heavily because this workflow is so much easier for docs and because I'm trying to help improve everything touching kubeadm as much as possible. But there's one outstanding issue wrt headings and intro content: you can't add a heading 1 to a topic to do what you wanted to do. The page title in the front matter is rendered as a heading 1 and everything else has to start at heading 2. (We still need to doc this better in the docs contributing content, I know.) Instead, I think we need to rewrite the top-of-page intro content to explain better the relationship between kube-dns and CoreDNS. I'm happy to write something, but I thought I'd push this commit first so you can see what I'm doing. Hope it's all clear -- ping here or on Slack with any questions ~ Jennifer * Interim fix for talking about CoreDNS * Fix CoreDNS details * PSP readOnly hostPath (#8898) * Add documentation for crictl (#8880) * Add documentation for crictl * Copyedit Signed-off-by: Misty Stanley-Jones <[email protected]> * Final copyedit * VolumeSubpathEnvExpansion alpha feature (#8835) * Note that Heapster is deprecated (#8827) * Note that Heapster is deprecated This notes that Heapster is deprecated, and migrates the relevant docs to talk about metrics-server or other solutions by default. * Copyedits and improvements Signed-off-by: Misty Stanley-Jones <[email protected]> * Address feedback * fix shortcode to troubleshoot deploy (#9057) * update dynamic kubelet config docs for v1.11 (#8766) * update dynamic kubelet config docs for v1.11 * Substantial copyedit * Address feedback * Reference doc for kubeadm (release-1.11) (#9044) * Reference doc for kubeadm (release-1.11) * fix shortcode to troubleshoot deploy (#9057) * Reference doc for kube-components (release-1.11) (#9045) * Reference doc for kube-components (release-1.11) * Update cloud-controller-manager.md * fix shortcode to troubleshoot deploy (#9057) * Documentation on lowercasing kubeadm init apiserver SANs (#9059) * Documentation on lowercasing kubeadm init apiserver SANs * fix shortcode to troubleshoot deploy (#9057) * Clarification in dynamic Kubelet config doc (#9061) * Promote sysctls to Beta (#8804) * Promote sysctls to Beta * Copyedits Signed-off-by: Misty Stanley-Jones <[email protected]> * Review comments * Address feedback * More feedback * kubectl reference docs for 1.11 (#9080) * Update Kubernetes API 1.11 ref docs (#8977) * Update v1alpha1 to v1beta1. * Adjust left nav for 1.11 ref docs. * Trim list of old ref docs. * Update Federation API ref docs for 1.11. (#9064) * Update Federation API ref docs for 1.11. * Add titles. * Update definitions.html * CRD versioning Public Documentation (#8834) * CRD versioning Public Documentation * Copyedit Signed-off-by: Misty Stanley-Jones <[email protected]> * Address feedback * More rewrites * Address feedback * Update main CRD page in light of versioning * Reorg CRD docs * Further reorg * Tweak title * CSI documentation update for raw block volume support (#8927) * CSI documetation update for raw block volume support * minor edits for "CSI raw block volume support" Some small grammar and style nits. * minor CSIBlockVolume edits * Update kubectl component ref page for 1.11. (#9094) * Update kubectl component ref page for 1.11. * Add title. Replace stevepe with username. * crd versioning doc: fix nits (#9142) * Update `DynamicKubeletConfig` feature to beta (#9110) xref: kubernetes/kubernetes#64275 * Documentation for dynamic volume limits based on node type (#8871) * add cos for storage limits * Update docs specific for aws and gce * fix some minor things * Update storage-limits.md * Add k8s version to feature-state shortcode * The Doc update for ScheduleDaemonSetPods (#8842) Signed-off-by: Da K. Ma <[email protected]> * Update docs related to PersistentVolumeLabel admission control (#9109) The said admission controller is disabled by default in 1.11 (kubernetes/kubernetes#64326) and scheduled to be removed in future release. * client exec auth: updates for 1.11 (#9154) * Updates HA kubeadm docs (#9066) * Updates HA kubeadm docs Signed-off-by: Chuck Ha <[email protected]> * kubeadm HA - Add stacked control plane steps * ssh instructions and some typos in the bash scripts Signed-off-by: Chuck Ha <[email protected]> * Fix typos and copypasta errors * Fix rebase issues * Integrate more changes Signed-off-by: Chuck Ha <[email protected]> * copyedits, layout and formatting fixes * final copyedits * Adds a sanity check for load balancer connection Signed-off-by: Chuck Ha <[email protected]> * formatting fixes, copyedits * fix typos, formatting * Document the Pod Ready++ feature (#9180) Closes: #9107 Xref: kubernetes/kubernetes#64057 * Mention 'KubeletPluginsWatcher' feature (#9177) * Mention 'KubeletPluginsWatcher' feature This feature is more developers oriented than users oriented, so simply mention it in the feature gate should be fine. In future, when the design doc is migrated from Google doc to the kubernetes/community repo, we can add links to it for users who want to dig deeper. Closes: #9108 Xref: kubernetes/kubernetes#63328, kubernetes/kubernetes#64605 * Copyedit * Amend dynamic volume list docs (#9181) The dynamic volume list feature has been documented but the feature gate related was not there yet. Closes: #9105 * Document for service account projection (#9182) This adds docs for the service account projection feature. Xref: kubernetes/kubernetes#63819, kubernetes/community#1973 Closes: #9102 * Update pod priority and preemption user docs (#9172) * Update pod priority and preemption user docs * Copyedit * Documentation on setting node name with Kubeadm (#8925) * Documentation on setting node name with Kubeadm * copyedit * Add kubeadm upgrade docs for 1.11 (#9089) * Add kubeadm upgrade docs for 1.11 * Initial docs review feedback * Add 1-11 to outline * Fix formatting on tab blocks * Move file to correct location * Add `kubeadm upgrade node config` step * Overzealous ediffing * copyedit, fix lists and headings * clarify --force flag for fixing bad state * Get TOML ready for 1.11 release * Blog post for 1.11 release (#9254) * Blog post for 1.11 release * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md * Update 2018-06-26-kubernetes-1.11-release-announcement.md
Fixes kubernetes/kubeadm#916
Not 100% complete, because we need to test once stable goes out, but as complete as we can before the packages go out.