Description
As announced previously, the legacy Kubernetes package repositories (apt.kubernetes.io
and yum.kubernetes.io
, also known as packages.cloud.google.com
) have been shut down (removed) as of 2024-03-04.
What does this mean for me?
If you use these legacy Kubernetes package repositories, you'll encounter errors upon using your package manager. In this case, you need to take steps outlined in this issue to resolve the problem.
How can I recognize if I'm affected by this?
If you use apt
(apt-get
), you're likely to get an error upon running apt update
(apt-get update
). Example errors include:
Ign:9 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
Err:10 https://packages.cloud.google.com/apt kubernetes-xenial Release
404 Not Found [IP: xxx.xxx.xxx.xxx 443]
Reading package lists... Done
E: The repository ‘https://apt.kubernetes.io/ kubernetes-xenial Release’ no longer has a Release file.
If you use yum
(or dnf
), you're likely to get an error upon running any yum
or dnf
command. Example errors include:
Error during downloading metadata for repository 'kubernetes':
- Status code: 404 for https://packages.cloud.google.com/yum/repos/kubernetes-el7-x85_64/repodata/repomd.xml (IP: xxx.xxx.xxx.xxx)
Error: Failed to download metadata for repo 'kubernetes': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
How to mitigate?
Please see the deprecation announcement and the pkgs.k8s.io announcement blog posts for more details.
In short, you need to:
- migrate to the Kubernetes official package repositories (
pkgs.k8s.io
) - if you don't need Kubernetes repositories on your system any longer, or if there's no Kubernetes version that you need in the official Kubernetes package repositories, you can just delete the legacy Kubernetes repositories from your system
- if you followed the official Kubernetes documentation to set up the legacy repositories, you'll likely find these repositories defined in
/etc/apt/sources.list.d/kubernetes.list
(forapt
users) or/etc/yum.repos.d/kubernetes.repo
(foryum
/dnf
users)
- if you followed the official Kubernetes documentation to set up the legacy repositories, you'll likely find these repositories defined in
Where can I get support for this?
We'll be following up on potential mitigations for users affected by this in the coming days. Please keep an eye on this issue if you're affected.
Activity