Additional clarifications for changing package repository

Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
pull/43918/head
Marko Mudrinić 2023-11-13 13:36:11 +01:00
parent ea4ba42f7f
commit 3f2b3a3691
No known key found for this signature in database
1 changed files with 21 additions and 4 deletions

View File

@ -6,11 +6,28 @@ weight: 120
<!-- overview --> <!-- overview -->
This page explains how to enable a package repository for a new Kubernetes minor release This page explains how to enable a package repository for the desired
Kubernetes minor release upon upgrading a cluster. This is only needed
for users of the community-owned package repositories hosted at `pkgs.k8s.io`. for users of the community-owned package repositories hosted at `pkgs.k8s.io`.
Unlike the legacy package repositories, the community-owned package repositories are Unlike the legacy package repositories, the community-owned package
structured in a way that there's a dedicated package repository for each Kubernetes repositories are structured in a way that there's a dedicated package
minor version. 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 >}}
## {{% heading "prerequisites" %}} ## {{% heading "prerequisites" %}}