Change:
The pull requests in question are essentially backports of documentation that already exists on the branch. We prefer to first resolve these issues in the branch and then proceed with backporting. Considering that the most recent releases have yet to be integrated into our legacy repositories, it's crucial that we expedite updating our documentation and instructions. We are going to merge these PRs and carry out any further backports as needed once we reach a consensus on the changes.
/sig docs /language en
/triage accepted
/priority important-soon I'd accept important-longterm instead.
/lifecycle frozen
All backport PRs merged. /close
Closing this issue. <detailsIn response to : All backport PRs merged. 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
This is about fixing remaining comments from the backport PRs, which is yet TBD /reopen
Reopened this issue. <detailsIn response to : This is about fixing remaining comments from the backport PRs, which is yet TBD /reopen 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
We still need to backport /reopen
Reopened this issue. <detailsIn response to : We still need to backport /reopen 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
Backports created:
Backports are merged /close
Closing this issue. <detailsIn response to : Backports are merged /close 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

Discussion:
<!-- overview --> <del> This page explains how to enable a package repository for a new Kubernetes minor release </del> <ins> This page explains how to enable a package repository for the desired Kubernetes minor release upon upgrading a cluster. This is only needed </ins> for users of the community-owned package repositories hosted at `pkgs.k8s.io`. <del> Unlike the legacy package repositories, the community-owned package repositories are structured in a way that there's a dedicated package repository for each Kubernetes minor version. </del> <ins> Unlike the legacy package repositories, the community-owned package repositories are structured in a way that there's a dedicated package repository for each Kubernetes minor version. {{< note >}} This guide only covers a part of the Kubernetes upgrade process. Please see the [upgrade guide](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/) for more information about upgrading Kubernetes clusters. {{</ note >}} {{< note >}} This step is only needed upon upgrading a cluster to another **minor** release. If you're upgrading to another patch release within the same minor release (e.g. v{{< skew currentVersion >}}.5 to v{{< skew currentVersion >}}.7), you don't need to follow this guide. However, if you're still using the legacy package repositories, you'll need to migrate to the new community-owned package repositories before upgrading (see the next section for more details on how to do this). {{</ note >}} </ins> ## {{% heading "prerequisites" %}}