Add kubeadm 1.9 upgrade docs #6485

jamiehannaford · 2017-11-29T11:21:58Z

Provides explicit instructions on how to upgrade to 1.9. Much of this was copy pasta'd from our 1.8 docs, so if there's a better way to document this I'm open to alternatives.

/cc @luxas

This change is

k8sio-netlify-preview-bot · 2017-11-29T11:26:16Z

Deploy preview ready!

Built with commit 30a9a25

https://deploy-preview-6485--kubernetes-io-master-staging.netlify.com

zacharysarah

Looks good! ✨ Some small changes for clarity and consistency.

zacharysarah · 2017-11-30T21:11:14Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+- `kubeadm upgrade` now allows you to upgrade etcd. To do so, use the appropriate flag.
+- Note that `kubeadm upgrade` will not touch any of your workloads, only Kubernetes-internal components. As a best-practice you should back up what's important to you. For example, any app-level state, such as a database an app might depend on (like MySQL or MongoDB) must be backed up beforehand.
+
+Also, note that only one minor version upgrade is supported. That is, you can only upgrade from, say 1.8 to 1.9, not from 1.7 to 1.9.


Also, note that only one minor version upgrade is supported. For example, you can only upgrade from 1.8 to 1.9, not from 1.7 to 1.9.

zacharysarah · 2017-11-30T21:11:54Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+## Upgrading your control plane
+
+You have to carry out the following steps by executing these commands on your master node:


Execute these commands on your master node:

zacharysarah · 2017-11-30T21:13:21Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+```
+
+**Caution:** Upgrading the `kubeadm` package on your system prior to upgrading the control plane causes a failed upgrade. 
+Even though `kubeadm` is shipped in the Kubernetes repositories, it's important to install `kubeadm` manually. The kubeadm 


Even though `kubeadm` ships in the Kubernetes repositories, it's important to install `kubeadm` manually.

So:

Even though kubeadm ships in the Kubernetes repositories, it's important to install kubeadm manually.

zacharysarah · 2017-11-30T21:13:40Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+team is working on fixing this limitation. 
+{: .caution}
+
+Verify that this download of kubeadm works, and has the expected version:


Verify that this download of kubeadm works and has the expected version:

zacharysarah · 2017-11-30T21:16:58Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+```
+
+2. If this the first time you use `kubeadm upgrade`, you will need to create a ConfigMap in order to preserve the 
+configuration for future upgrades. Note that for the below command, you will need to recall what CLI args you 


2. If this your first time using `kubeadm upgrade`, you need to [create a ConfigMap](/docs/tasks/configure-pod-container/configmap/) in order to preserve the configuration for future upgrades. Note that for the following command, you will need to recall what command line arguments you passed to `kubeadm init` the first time.

So:

If this your first time using kubeadm upgrade, you need to create a ConfigMap in order to preserve the configuration for future upgrades. Note that for the following command, you will need to recall what command line arguments you passed to kubeadm init the first time.

zacharysarah · 2017-11-30T21:24:20Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+5. Manually upgrade your Software Defined Network (SDN).
+
+   Your Container Network Interface (CNI) provider might have its own upgrade instructions to follow now.


Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow.

So:

Your Container Network Interface (CNI) provider may have its own upgrade instructions to follow.

zacharysarah · 2017-11-30T21:24:48Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+   find your CNI provider and see if there are additional upgrade steps
+   necessary.
+
+6. Add RBAC permissions for automated certificate rotation. In the future, kubeadm will perform this step automatically:


6. Add RBAC permissions for automated certificate rotation.

This is not needed anymore kubeadm does this automatically now

zacharysarah · 2017-11-30T21:26:16Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+If the `STATUS` column of the above command shows `Ready` for all of your hosts, you are done.
+
+## Recovering from a bad state


## Recovering from a failure state

zacharysarah · 2017-11-30T21:27:17Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+## Recovering from a bad state
+
+If `kubeadm upgrade` somehow fails and fails to roll back, due to an unexpected shutdown during execution for instance,


If `kubeadm upgrade` somehow fails and fails to roll back, for example due to an unexpected shutdown during execution,

So:

If kubeadm upgrade somehow fails and fails to roll back, for example due to an unexpected shutdown during execution,

zacharysarah · 2017-11-30T21:28:03Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+## Recovering from a bad state
+
+If `kubeadm upgrade` somehow fails and fails to roll back, due to an unexpected shutdown during execution for instance,
+you may run `kubeadm upgrade` again as it is idempotent and should eventually make sure the actual state is the desired state you are declaring.


you can run `kubeadm upgrade` again.

jamiehannaford · 2017-12-01T12:02:42Z

Thanks for the review @zacharysarah, changes have been pushed.

@luxas ping for tech review

luxas

Thanks a lot @jamiehannaford for this 👏 👍
Left a few comments to fixup

luxas · 2017-12-02T11:36:02Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+- You need to have a functional `kubeadm` Kubernetes cluster running version 1.8.0 or higher in order to use the process described here.
+- 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. To do so, use the appropriate flag.


kubeadm upgrade enforces that you upgrade etcd to 3.1.10 as part of upgrading from v1.8 to v1.9. This is due to that etcd 3.1.10 is the officially validated etcd version for Kubernetes v1.9. The upgrade is handled automatically by kubeadm for you.

luxas · 2017-12-02T11:36:58Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+$ kubeadm version
+```
+
+2. 2. If this your first time using `kubeadm upgrade`, you need to [create a ConfigMap](/docs/tasks/configure-pod-container/configmap/) in order to preserve the configuration for future upgrades. Note that for the following command, you will need to recall what command line arguments you passed to `kubeadm init` the first time.


is 2. 2. here right?

This doesn't apply anymore, as all v1.8 and above clusters have the ConfigMap already. This was only a thing when upgrading from v1.7

luxas · 2017-12-02T11:40:37Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+   find your CNI provider and see if there are additional upgrade steps
+   necessary.
+
+6. Add RBAC permissions for automated certificate rotation. In the future, kubeadm will perform this step automatically:


This is not needed anymore kubeadm does this automatically now

luxas · 2017-12-02T11:42:35Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+```shell
+$ kubeadm upgrade apply v1.9.0
+[preflight] Running pre-flight checks


If you try to do a kubeadm upgrade apply v1.9.0-beta.1 with kubeadm from HEAD locally, I think the output will be a bit different (also considering etcd upgrades etc.). Can you please paste the latest output?

Actually, now did it for you :)

kubeadm upgrade apply v1.9.0 [preflight] Running pre-flight checks. [upgrade] Making sure the cluster is healthy: [upgrade/config] Making sure the configuration is correct: [upgrade/config] Reading configuration from the cluster... [upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml' [upgrade/version] You have chosen to upgrade to version "v1.9.0" [upgrade/versions] Cluster version: v1.8.1 [upgrade/versions] kubeadm version: v1.9.0 [upgrade/confirm] Are you sure you want to proceed with the upgrade? [y/N]: y [upgrade/prepull] Will prepull images for components [kube-apiserver kube-controller-manager kube-scheduler] [upgrade/apply] Upgrading your Static Pod-hosted control plane to version "v1.9.0"... [etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests802453804/etcd.yaml" [upgrade/staticpods] Moved upgraded manifest to "/etc/kubernetes/manifests/etcd.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests502223003/etcd.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [apiclient] Found 1 Pods for label selector component=etcd [upgrade/staticpods] Component "etcd" upgraded successfully! [upgrade/staticpods] Writing upgraded Static Pod manifests to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests802453804" [controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests802453804/kube-apiserver.yaml" [controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests802453804/kube-controller-manager.yaml" [controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/tmp/kubeadm-upgraded-manifests802453804/kube-scheduler.yaml" [upgrade/staticpods] Moved upgraded manifest to "/etc/kubernetes/manifests/kube-apiserver.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests502223003/kube-apiserver.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [apiclient] Found 1 Pods for label selector component=kube-apiserver [upgrade/staticpods] Component "kube-apiserver" upgraded successfully! [upgrade/staticpods] Moved upgraded manifest to "/etc/kubernetes/manifests/kube-controller-manager.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests502223003/kube-controller-manager.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [apiclient] Found 1 Pods for label selector component=kube-controller-manager [upgrade/staticpods] Component "kube-controller-manager" upgraded successfully! [upgrade/staticpods] Moved upgraded manifest to "/etc/kubernetes/manifests/kube-scheduler.yaml" and backed up old manifest to "/etc/kubernetes/tmp/kubeadm-backup-manifests502223003/kube-scheduler.yaml" [upgrade/staticpods] Waiting for the kubelet to restart the component [apiclient] Found 1 Pods for label selector component=kube-scheduler [upgrade/staticpods] Component "kube-scheduler" upgraded successfully! [uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [bootstraptoken] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials [bootstraptoken] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token [bootstraptoken] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster [addons] Applied essential addon: kube-dns [addons] Applied essential addon: kube-proxy [upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.9.0". Enjoy! [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets in turn.

luxas · 2017-12-02T11:43:09Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+Controller Manager   v1.8.1    v1.8.6
+Scheduler            v1.8.1    v1.8.6
+Kube Proxy           v1.8.1    v1.8.6
+Kube DNS             1.14.4    1.14.4


nit: I think the kube-dns version should be 1.14.5 for 1.8.6

luxas · 2017-12-02T11:45:08Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+- luxas
+- roberthbailey
+- jbeda
+title: Upgrading kubeadm clusters from 1.8 to 1.9


We now support downgrades as well; can we rephrase this to be sth like Upgrading/downgrading kubeadm clusters between v1.8 and v1.9?

luxas · 2017-12-02T11:45:45Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+{% capture steps %}
+
+## Upgrading your control plane


Please add a section for downgrades below as well

And note that etcd WILL NOT be downgraded if you do v1.8 (3.0.17) -> v1.9 (3.1.10) -> v1.8 (3.1.10) but that it shouldn't technically be a problem

luxas · 2017-12-02T11:46:09Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+
+Before proceeding:
+
+- You need to have a functional `kubeadm` Kubernetes cluster running version 1.8.0 or higher in order to use the process described here.


We could mention again here that swap needs to be disabled, just in case it helps someone.

luxas · 2017-12-02T11:47:18Z

docs/setup/independent/create-cluster-kubeadm.md

@@ -511,6 +511,8 @@ Instructions for upgrading kubeadm clusters are available for:
 * [1.7.x to 1.7.y  upgrades](/docs/tasks/administer-cluster/kubeadm-upgrade-1-8/)
 * [1.7 to 1.8 upgrades](/docs/tasks/administer-cluster/kubeadm-upgrade-1-8/)
 * [1.8.x to 1.8.y upgrades](/docs/tasks/administer-cluster/kubeadm-upgrade-1-8/)
+ * [1.8 to 1.9 upgrades](/docs/tasks/administer-cluster/kubeadm-upgrade-1-9/)


upgrades/downgrades

luxas · 2017-12-02T12:00:33Z

docs/tasks/administer-cluster/kubeadm-upgrade-1-9.md

+```shell
+$ kubectl create clusterrolebinding kubeadm:node-autoapprove-certificate-rotation --clusterrole=system:certificates.k8s.io:certificatesigningrequests:selfnodeclient --group=system:nodes
+```
+


We might want to add an "optional features selection during upgrades" or similar section...
And describe that you can set --feature-gates CoreDNS=true and that'll swap out kube-dns for CoreDNS for you automatically without downtime and/or enable --feature-gates SelfHosting=true which will give you a self-hosted cluster at the same time.

Somewhere here we should also mention certificate rotation and say that if the /etc/kubernetes/pki/apiserver.crt cert expires in less than 180 days old when upgrading, kubeadm will move /etc/kubernetes/pki/apiserver.{crt,key} to /etc/kubernetes/pki/expired and generate a new serving certificate.

zacharysarah · 2017-12-07T04:55:19Z

@jamiehannaford 👋

I changed the base to release-1.9 because docs has a different relationship with master and feature branches.
Bumping for updates to review feedback from @luxas (thanks!).

zacharysarah · 2017-12-07T20:48:38Z

@jamiehannaford 👋 Bumping for a response to review feedback. Deadline for completion is tomorrow, Friday, December 8th.

/cc @idvoretskyi

jamiehannaford · 2017-12-08T15:40:44Z

@zacharysarah @luxas All changes incorporated. The only one I didn't have time for is adding a section for downgrades. Is this a blocker or can we add in a PR after the docs freeze? We have most of the content here. I don't mind either way.

k8sio-netlify-preview-bot · 2017-12-08T15:41:58Z

Deploy preview ready!

Built with commit 33e4ae8

https://deploy-preview-6485--kubernetes-io-vnext-staging.netlify.com

luxas

/lgtm

zacharysarah · 2017-12-11T19:38:25Z

@jamiehannaford I'm fine with making an update after release. 👍

* Trivial change to open release branch * Undo trivial change * add service ipvs overview * Add instructions on how to setup kubectl * Document conntrack dependency for kube-proxy * Add an a This is kind of jarring / missing an article. I'm guessing it should either be ' to a rack of bare metal servers.' or '...to racks of bare metal servers.'. * adding example responses for common issues - support request - code bug report * Trivial change to open release branch * Undo trivial change * Signed-off-by: Ziqi Zhao <zhaoziqi@qiniu.com> (#5366) Fix the not-working test case yaml for /doc/concepts/storage/volumes.md * kubectl-overview * temp fix for broken pod and deployment links * Update Table of Solutions for Juju * Revise certificates documentation (#5965) * Update review-issues.md Some edits for clarity and condensed language. * Update init-containers.md Fix leading spaces in commands. * Update kubectl-overview.md Fix format. * Update clc.md Fix format. * Update openstack-heat.md The url no need. just highlight. * Typo I believe this should be "users" not "uses" * making explicit hostname uniq requirement * Update scheduling-hugepages.md * Update update-daemon-set.md * fix redirection of PersistentVolume * Update hpa.md * update kubectl instruction * Use the format of kubeadm init * fix spelling error guarnatees to guarantees * add matchLabels description (#6020) * search and replace for k8s.github.io to website (#6019) * fix scale command of object-management (#6011) * Update replicaset.md (#6009) * Update secret.md (#6008) * specify password for mysql image (#5990) * specify password for mysql image * specify password for mysql image * link error for run-stateless-application-deployment.md (#5985) * link error for run-stateless-application-deployment.md * link error for run-stateless-application-deployment.md * Add performance implications of inter-pod affinity/anti-affinity (#5979) * 404 monthly maintenance - October 2017 (#5977) * Updated redirects * More redirects * Add conjure-up to Turnkey Cloud Solutions list (#5973) * Add conjure-up to Turnkey Cloud Solutions list * Changed wording slightly * change the StatefulSet to ReplicaSet in reference (#5968) * Clarification of failureThreshold of probes (#5963) * Mention usage of block storage version param (#5925) Mention usage of block storage version (bs-version) parameter to workaround attachment issues using older K8S versions on an OpenStack cloud with path-based endpoints. Resolves: #5924 * Update sysctl-cluster.md (#5894) Include guide on enabling unsafe sysctls in minikube * Avoid Latin phrases & format note (#5889) * Avoid Latin phrases & format note according the Documentation Style Guide * Update scratch.md * Update scratch.md * resolves jekyll rendering error (#5976) - chinese isn't understood for keys in YAML frontmatter in jekyll, so replaced it with the english equivalent that doesn't throw the following error on rendering: Error reading file src/kubernetes.github.io/cn/docs/concepts/cluster-administration/device-plugins.md: (<unknown>): could not find expected ':' while scanning a simple key at line 4 column 1 * Change VM to pod. (#6022) * Add link to custom metrics. (#6023) * Rephrase core group. (#6024) * Added explanation on context to when joining (#6018) * Update create-cluster-kubeadm.md (#5761) Update Canal version in pod network apply commands * Fixes issue #5620 (#5869) * Fixes issue #5620 Signed-off-by: Brad Topol <btopol@us.ibm.com> * Restructured so that review process is for both current and upcoming releases. Added content describing the use of tech reviewers. * Removed incorrect Kubernetes reviewer link. * Fixed tech reviewer URL to now use website * Update pod-priority-preemption.md fix-wrong-link-to-pod-preemption * pod-security-policy.md: add links to the page about admission plugins. * Adding all files for BlaBlaCar case study (#5857) * Adding all files for BlaBlaCar case study * Update blablacar.html * Fix changed URL for google containers * Add /docs/reference/auto-generated directory * correct the downwardapi redirect * Remove links using "here" * Rename to /docs/reference/generated directory * add Concept template * Change title to just Ingress * Link mistake (#6038) * link mistake * link mistake * skip title check for skip_title_check.txt * skip title check for skip_title_check.txt * remove doesn't exist link. * Fix podpreset task (#5705) * Add a simple pod manifest to pod overview (#5986) * Split PodPreset concept out from task doc (#5984) * Add selector spec description (#5789) * Add selector spec description * Fix selector field explanation * Put orphaned topics in TOC. (#6051) * static-pod example bad format in the final page (#6050) * static-pod example bad format in the final page * static-pod example bad format in the final page * static-pod example bad format in the final page * static-pod example bad format in the final page * static-pod example bad format in the final page * Fix `backoffLimit` field misplacement (#6042) It should be placed in JobSpec according to: https://github.com/kubernetes/kubernetes/blob/master/api/swagger-spec/batch_v1.json#L1488-L1514 * Update addons.md (#6061) * add info about VMware NSX-T CNI plugin (#5987) * add info about VMware NSX-T CNI plugin Hello, I'm VMware Networking and Security Architect and would like to include short information about our CNI plugin implementation similar to what other vendors did Best regards Emil Gagala * Update networking.md * Update networking.md * Update networking.md * Update: Using universal zsh configuration (#5669) * Update install-kubectl.md Zsh is not only oh-my-zsh, so I added universal configuration for zsh that also can be used in prezto. * fix merge error after rebase * Operating etcd cluster for Kubernetes bad format in the final page (#6056) * Operating etcd cluster for Kubernetes bad format in the final page * Update configure-upgrade-etcd.md * Update configure-upgrade-etcd.md * Usage note and warning tags. (#6053) * Usage note and warning tags. * Update configure-upgrade-etcd.md * Update configure-upgrade-etcd.md * Document jekyll includes snippets * Add jekyll includes to docs home toc - Remove extra kubernetes home in toc * document docker cgroupdriver req (#5937) * Update test blacklists (#6063) * Update toc check blacklist * Update title check blacklist * wip * wip * Fix typo * Document unconfined apparmor profile * Revert "Document the unconfined profile for AppArmor" (#6268) * CRD Validation: remove alpha warning, change enable instructions to (#6066) disable * Documented service annotation for AWS ELB SSL policy * kubeadm: add a note about the new `--print-join-command` flag. This is a new flag for the `kubeadm token create` command. * Add a note to PDB page * Improve Kubeadm reference doc (#6103) * automatically-generated kubeadm reference doc * user-mantained kubeadm reference doc * Documentation for CSIPersistentVolume * change replicaset documentation to use apps/v1 APIs * Update service.md ipvs alpha version -> beta version * Updated Deployment concept docs (#6494) * Updated Deployment concept docs * Addressed comments * Documentation for volume scheduling alpha feature * Update admission control docs for webhooks * Improve DNS documentation (#6479) * update ds for 1.9 * Update service.md * Update service.md * Revert "begin updating webhook documentation" (#6575) * Update version numbers to include 1.9 (#6518) * Update site versions for 1.9 * Removed 1.4 docs * Update _config.yml * Update _config.yml * updates for raw block devices * rbac: docs for aggregated cluster roles (#6474) * Added IPv6 information for Kubelet arguments (#6498) * Added IPv6 info to kube-proxy arguments * Added IPv6 information for argument for kubelet * Update PVC resizing documentation (#6487) * Updates for Windows Server version 1709 with K8s v1.8 (#6180) * Updated for WSv1709 and K8s v1.8 * Updated picture and CNI config * Fixed formatting on CNI Config * Updated docs to reference Microsoft/SDN GitHub docs * fix typo * Workaround for Jekyllr frontmatter * Added section on features and limitations, with example yaml files. * Update index.md * Added kubeadm section, few other small fixes * Few minor grammar fixes * Update access-cluster.md with a comment that for IPv6 the user should use [::1] for the localhost * Addressed a number of issues brought up against the base PR * Fixed windows-host-setup link * Rewrite PodSecurityPolicy guide * Update index.md Signed-off-by: Alin Balutoiu <abalutoiu@cloudbasesolutions.com> Signed-off-by: Alin Gabriel Serdean <aserdean@ovn.org> * Spelling correction and sentence capitalization. - Corrected the spelling error for storing, was put in as 'stoing'. - Capitalized list items. - Added '.' at end of sentences in the list items. * Update index.md * Update index.md * Addressed comments and rebased * Fixed formatting * Fixed formatting * Updated header link * Updated hyperlinks * Updated warning * formatting * formatting * formatting * Revert "Update access-cluster.md with a comment that for IPv6" This reverts commit 31e4dbd. * Revert "fix typo" This reverts commit c056787. * Revert "Workaround for Jekyllr frontmatter" This reverts commit b84ac59. * Fixed grammatical issues and reverted non-related commits * Revert "Rewrite PodSecurityPolicy guide" This reverts commit 5d39cfe. * Revert "Spelling correction and sentence capitalization." This reverts commit 47eed43. * Fixed auto-numbering * Minor formatting updates * CoreDNS feature documentation (#6463) * Initial placeholder PR for CoreDNS feature documentation * Remove from admin, add content * Fix missing endcapture * Add to tasks.yml * Review feedback * Postpone Deletion of a Persistent Volume Claim in case It Is Used by a Pod (#6415) * Postpone Deletion of a Persistent Volume Claim in case It Is Used by a Pod A new feature PVC Protection was added into K8s 1.9 that's why this documentation change is needed. * Added tag at the top of each new area. * Fix typo * Fix: switched on in (all kubelets) -> (all K8s components). * Added link to admission controller * Moved PVC Protection configuration into Before you begin section. * Added steps how to verify PVC Protection feature. * Fixes for admission controller plugin description and for PVC Protection description in PVC lifecycle. * Testing official rendering of enumerations (1., 2., 3., etc.) * Re-write to address comments from review. * Fixed definition when a PVC is in active use by a pod. * Change auditing docs page for 1.9 release (#6427) * Change auditing docs page for 1.9 release Signed-off-by: Mik Vyatskov <vmik@google.com> * Address review comments Signed-off-by: Mik Vyatskov <vmik@google.com> * Address review comments Signed-off-by: Mik Vyatskov <vmik@google.com> * Address review comments Signed-off-by: Mik Vyatskov <vmik@google.com> * Fix broken link Signed-off-by: Mik Vyatskov <vmik@google.com> * short circuit deny docs (#6536) * line wrap * short circuit deny * address comments * Add kubeadm 1.9 upgrade docs (#6485) * kubeadm: Improve kubeadm documentation for v1.9 (#6645) * Update admission control docs for webhooks (re-send #6368) (#6650) * Update admission control docs for webhooks * update in response to comments * Revamp rkt and add CRI-O as alternative runtime (#6371) Signed-off-by: Lorenzo Fontana <lo@linux.com> * Documented NLB for Kubernetes 1.9 (#6260) * Added IPV6 information to setup cluster using kubeadm (#6465) * 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 * StatefulSet 1.9 updates. (#6550) * updates sts concept and tutorials to use 1.9 apps/v1 * Update statefulset.md * clarify pod name label * Garbage collection updates for 1.9 (#6555) * 1.9 gc policy update * carify deletion * Couple nits for dnsConfig doc (#6652) * Add doc for AllowedFlexVolume (#6563) * Update OpenStack Cloud Provider API support for v1.9 (#6638) * Flex volume is GA. Remove alpha notation. (#6666) * Update generated ref docs for Kubernetes and Federation components. (#6658) * Update generated ref docs for Kubernetes and Federation components. * Rename kubectl-options to kubectl. * Add title to kubectl. * Fix double synopsis. * Update Federation API ref docs for 1.9. (#6636) * Update federation API ref docs. * Move and redirect. * Move generated Federation docs to the generated directory. * Fix titles. * Type * Fix titles * Update auto-generated Kubernetes APi ref docs. (#6646) * Update kubectl commands for 1.9 (#6635) * add ExtendedResourceToleration admission controller (#6618) * Update API reference paths for v1.9 (#6681)

k8s-ci-robot requested a review from luxas November 29, 2017 11:21

k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Nov 29, 2017

k8s-github-robot assigned zacharysarah Nov 29, 2017

steveperry-53 added Needs Docs Review labels Nov 29, 2017

zacharysarah suggested changes Nov 30, 2017

View reviewed changes

zacharysarah added Docs Review: Open Issues and removed Needs Docs Review labels Nov 30, 2017

jamiehannaford force-pushed the kubeadm-upgrade-19 branch from 31702c7 to 30a9a25 Compare December 1, 2017 12:02

zacharysarah approved these changes Dec 1, 2017

View reviewed changes

zacharysarah added Docs LGTM and removed Docs Review: Open Issues labels Dec 1, 2017

luxas reviewed Dec 2, 2017

View reviewed changes

zacharysarah changed the base branch from master to release-1.9 December 7, 2017 04:53

zacharysarah added Tech Review: Open Issues and removed Needs Tech Review labels Dec 7, 2017

This was referenced Dec 7, 2017

Release 1.9 #5978

Merged

[1.9] Issue Burndown kubernetes/sig-release#38

Closed

k8s-ci-robot requested a review from idvoretskyi December 7, 2017 20:48

Add kubeadm 1.9 upgrade docs

33e4ae8

jamiehannaford force-pushed the kubeadm-upgrade-19 branch from 30a9a25 to 33e4ae8 Compare December 8, 2017 15:39

luxas approved these changes Dec 11, 2017

View reviewed changes

k8s-ci-robot assigned luxas Dec 11, 2017

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 11, 2017

zacharysarah added Tech Review LGTM and removed Tech Review: Open Issues labels Dec 11, 2017

zacharysarah merged commit 19cd936 into kubernetes:release-1.9 Dec 11, 2017


		## Upgrading your control plane

		You have to carry out the following steps by executing these commands on your master node:


		5. Manually upgrade your Software Defined Network (SDN).

		Your Container Network Interface (CNI) provider might have its own upgrade instructions to follow now.


		If the `STATUS` column of the above command shows `Ready` for all of your hosts, you are done.

		## Recovering from a bad state


		Before proceeding:

		- You need to have a functional `kubeadm` Kubernetes cluster running version 1.8.0 or higher in order to use the process described here.

Add kubeadm 1.9 upgrade docs #6485

Add kubeadm 1.9 upgrade docs #6485

Conversation

jamiehannaford commented Nov 29, 2017 • edited by k8s-reviewable Loading

k8sio-netlify-preview-bot commented Nov 29, 2017 • edited Loading

zacharysarah left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jamiehannaford commented Dec 1, 2017

luxas left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

zacharysarah commented Dec 7, 2017

zacharysarah commented Dec 7, 2017

jamiehannaford commented Dec 8, 2017

k8sio-netlify-preview-bot commented Dec 8, 2017

luxas left a comment

Choose a reason for hiding this comment

zacharysarah commented Dec 11, 2017

jamiehannaford commented Nov 29, 2017 •

edited by k8s-reviewable

Loading

k8sio-netlify-preview-bot commented Nov 29, 2017 •

edited

Loading