Code change:
This is a Bug Report <!-- Thanks for filing an issue! Before submitting, please fill in the following information. --<!-- See for guidance on writing an actionable issue description. --<!--Required Information--Problem: The page https://v1- explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.20.x to version 1.21.x, and from version 1.21.x to 1.21.y. (Should be from version 1.19.x to version 1.20.x, and from version 1.20.x to 1.20.y.) Proposed Solution: In Replace =- =- ... Page to Update: https://v1- <!--Optional Information (remove the comment tags around information you would like to include)--<!--Kubernetes Version:--<!--Additional Information:--/assign
I think we should fix the shortcode to use the documented version, rather than the most recent release. /sig cluster-lifecycle /language en
the intent behind seems to be misleading if is fed at build time pointing at the latest current k8s version. while extending the latestVersion shortcodes i expected to be static and hardcoded per k/website release branch. i can send PRs for this but i'd need to understand more about the "documented" version that you mentioned. i.e. making latestVersion fixed to 1.20 in the 1.20 release branch seems reasonable to me.
^ for additional opinions.
Despite a misleading name, is supposed to use not . AIUI.
i can see is being used in a few places: should all of these be modified to use or only the shortcodes in ? and for which branches - and ?
is useful, it does represent the most recent release.
ok, i can PR the change for 1.20, and master since this is only a problem for the kubeadm upgrade docs. is also used here, but the versions there are just examples. https://v1-
here are the PRs:
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-contributor-experience at . /lifecycle stale
/remove-lifecycle stale
/triage accepted
/priority-important longterm
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : /priority-important longterm Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/priority important-longterm

Related discussion:
text: ## Determine which version to upgrade to <del> Find the latest stable {{< skew latestVersion >}} version using the OS package manager: </del> <ins> Find the latest stable {{< skew currentVersion >}} version using the OS package manager: </ins> {{< tabs name="k8s_install_versions" >}} {{% tab name="Ubuntu, Debian or HypriotOS" %}} apt update apt-cache madison kubeadm <del> # find the latest {{< skew latestVersion >}} version in the list # it should look like {{< skew latestVersion >}}.x-00, where x is the latest patch </del> <ins> # find the latest {{< skew currentVersion >}} version in the list # it should look like {{< skew currentVersion >}}.x-00, where x is the latest patch </ins> {{% /tab %}} {{% tab name="CentOS, RHEL or Fedora" %}} yum list --showduplicates kubeadm --disableexcludes=kubernetes <del> # find the latest {{< skew latestVersion >}} version in the list # it should look like {{< skew latestVersion >}}.x-0, where x is the latest patch </del> <ins> # find the latest {{< skew currentVersion >}} version in the list # it should look like {{< skew currentVersion >}}.x-0, where x is the latest patch </ins> {{% /tab %}} {{< /tabs >}}