place holder for kubeadm upgrade#12919
place holder for kubeadm upgrade#12919RA489 wants to merge 2 commits intokubernetes:dev-1.14from RA489:patch-2
Conversation
|
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 6172b3b https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/5c8665314873770008cbf605 |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/sig cluster-lifecycle |
|
/sig cluster-lifecycle |
| The command `join --experimental-control-plane` is known to fail on single node clusters created with kubeadm v1.12 and then upgraded to v1.13.x. | ||
| This will be fixed when graduating the `join --control-plane` workflow from alpha to beta. | ||
| A possible workaround is described [here](https://github.com/kubernetes/kubeadm/issues/1269#issuecomment-441116249). | ||
| {{</ warning >}} |
There was a problem hiding this comment.
/assign @fabriziopandini
we technically don't need the above warning anymore for 1.13->1.14?
am i correct?
There was a problem hiding this comment.
I like the warning for folks who might be concerned.
|
|
||
| [upgrade/successful] SUCCESS! Your cluster was upgraded to "v1.14.0". Enjoy! | ||
|
|
||
| [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. |
There was a problem hiding this comment.
we might have to update the output once done testing. but this is good for now.
|
@kubernetes/sig-cluster-lifecycle-pr-reviews |
timothysc
left a comment
There was a problem hiding this comment.
Looks good with minor comments.
| The command `join --experimental-control-plane` is known to fail on single node clusters created with kubeadm v1.12 and then upgraded to v1.13.x. | ||
| This will be fixed when graduating the `join --control-plane` workflow from alpha to beta. | ||
| A possible workaround is described [here](https://github.com/kubernetes/kubeadm/issues/1269#issuecomment-441116249). | ||
| {{</ warning >}} |
There was a problem hiding this comment.
I like the warning for folks who might be concerned.
|
|
||
| {{< tabs name="k8s_install_kubeadm" >}} | ||
| {{% tab name="Ubuntu, Debian or HypriotOS" %}} | ||
| # replace x in 1.14.x-00 with the latest patch version |
There was a problem hiding this comment.
that -00 versioning doesn't look right to me.
There was a problem hiding this comment.
this is something we decided on last cycle
cc @mauilion
| [upgrade/kubelet] Now that your control plane is upgraded, please proceed with upgrading your kubelets if you haven't already done so. | ||
| ``` | ||
|
|
||
| 1. Manually upgrade your Software Defined Network (SDN). |
There was a problem hiding this comment.
Manually upgrade your CNI...
There was a problem hiding this comment.
Not everyone uses and SDN.
There was a problem hiding this comment.
we are just copy-pasting from the old docs for 1.13, but i guess we can make the change here.
2534806 to
ead0a28
Compare
|
closing in favor of: #13189 |
|
@neolit123: Closed this PR. DetailsIn 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. |
Place holder for kubeadm upgrade of kubernetes/kubeadm/issues/1422
/assign @neolit123