From 3f2b3a3691c5dfebba0ba299741d3c84a09750e5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marko=20Mudrini=C4=87?= Date: Mon, 13 Nov 2023 13:36:11 +0100 Subject: [PATCH] Additional clarifications for changing package repository MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Marko Mudrinić --- .../kubeadm/change-package-repository.md | 25 ++++++++++++++++--- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md b/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md index 0458f7c8ad..69492053d8 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/change-package-repository.md @@ -6,11 +6,28 @@ weight: 120 -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`. -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. +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 >}} +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). +{{}} ## {{% heading "prerequisites" %}}