Changing The Kubernetes Package Repository

This page explains how to switch from one Kubernetes package repository to another when upgrading Kubernetes minor releases. Unlike deprecated Google-hosted repositories, the Kubernetes package repositories are structured in a way that there’s a dedicated package repository for each Kubernetes minor version.

Before you begin

This document assumes that you’re already using the Kubernetes community-owned package repositories. If that’s not the case, it’s strongly recommend to migrate to the Kubernetes package repositories.

Verifying if the Kubernetes package repositories are used

If you’re unsure if you’re using the Kubernetes package repositories or the Google-hosted repository, take the following steps to verify:

Print the contents of the file that defines the Kubernetes apt repository:

  1. # On your system, this configuration file could have a different name
  2. pager /etc/apt/sources.list.d/kubernetes.list

If you see a line similar to:

  1. deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.27/deb/ /

You’re using the Kubernetes package repositories and this guide applies to you. Otherwise, it’s strongly recommend to migrate to the Kubernetes package repositories.

Print the contents of the file that defines the Kubernetes yum repository:

  1. # On your system, this configuration file could have a different name
  2. cat /etc/yum.repos.d/kubernetes.repo

If you see baseurl similar to the baseurl in the output below:

  1. [kubernetes]
  2. name=Kubernetes
  3. baseurl=https://pkgs.k8s.io/core:/stable:/v1.27/rpm/
  4. enabled=1
  5. gpgcheck=1
  6. gpgkey=https://pkgs.k8s.io/core:/stable:/v1.27/rpm/repodata/repomd.xml.key
  7. exclude=kubelet kubeadm kubectl

You’re using the Kubernetes package repositories and this guide applies to you. Otherwise, it’s strongly recommend to migrate to the Kubernetes package repositories.

Note:

The URL used for the Kubernetes package repositories is not limited to pkgs.k8s.io, it can also be one of:

  • pkgs.k8s.io
  • pkgs.kubernetes.io
  • packages.kubernetes.io
  • packages.kubernetes.io

Switching to another Kubernetes package repository

This step should be done upon upgrading from one to another Kubernetes minor release in order to get access to the packages of the desired Kubernetes minor version.

  1. Open the file that defines the Kubernetes apt repository using a text editor of your choice:
  1. nano /etc/apt/sources.list.d/kubernetes.list

You should see a single line with the URL that contains your current Kubernetes minor version. For example, if you’re using v1.27, you should see this:

  1. deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.27/deb/ /
  1. Change the version in the URL to the next available minor release, for example:
  1. deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.28/deb/ /

  1. Save the file and exit your text editor. Continue following the relevant upgrade instructions.

  2. Open the file that defines the Kubernetes yum repository using a text editor of your choice:

  1. nano /etc/yum.repos.d/kubernetes.repo

You should see a file with two URLs that contain your current Kubernetes minor version. For example, if you’re using v1.27, you should see this:

  1. [kubernetes]
  2. name=Kubernetes
  3. baseurl=https://pkgs.k8s.io/core:/stable:/v1.27/rpm/
  4. enabled=1
  5. gpgcheck=1
  6. gpgkey=https://pkgs.k8s.io/core:/stable:/v1.27/rpm/repodata/repomd.xml.key
  7. exclude=kubelet kubeadm kubectl cri-tools kubernetes-cni
  1. Change the version in these URLs to the next available minor release, for example:
  1. [kubernetes]
  2. name=Kubernetes
  3. baseurl=https://pkgs.k8s.io/core:/stable:/vv1.28/rpm/
  4. enabled=1
  5. gpgcheck=1
  6. gpgkey=https://pkgs.k8s.io/core:/stable:/vv1.28/rpm/repodata/repomd.xml.key
  7. exclude=kubelet kubeadm kubectl cri-tools kubernetes-cni
  1. Save the file and exit your text editor. Continue following the relevant upgrade instructions.

What’s next