Welcome to the Linux Foundation Forum!

Exercise 8.2: Creating a Persistent NFS Volume (PV) -- W: GPG error:

HiEveryone, I need help resolving this GPG error below: I tried googling it but couldn't find the right solution.

Thanks.

aleop@cp:~$ sudo apt-get update && sudo apt-get install -y nfs-kernel-server
Hit:1 https://download.docker.com/linux/ubuntu focal InRelease
Hit:3 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal InRelease
Hit:4 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal-backports InRelease
Get:2 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.29/deb InRelease [1186 B]
Hit:6 http://security.ubuntu.com/ubuntu focal-security InRelease
Err:2 https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.29/deb InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 234654DA9A296436
Reading package lists... Done
W: GPG error: **https://prod-cdn.packages.k8s.io/repositories/isv:/kubernetes:/core:/stable:/v1.29/deb InRelease: The following signatures couldn't be verified because the public key is not available: **NO_PUBKEY 234654DA9A296436
E: The repository 'https://pkgs.k8s.io/core:/stable:/v1.29/deb InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Comments

  • Posts: 2,443
    edited April 2024

    Hi @oophilip,

    I have seen a similar behavior of the apt repos for Kubernetes reported for a cluster hosted on AWS EC2. It seems the Kubernetes repos are somehow modified after the installation and upgrade steps from the earlier labs 3 and 4, and can no longer be validated by the apt package manager.

    Option #1:
    Try running each command separately - first the update command (even if it errors out about the Kubernetes v1.29 repo), then run the install of the nfs package.

    Option #2 (if Option #1 does not install the nfs package):
    Assuming your nodes are already on the desired Kubernetes version 1.29.1, remove the apt repository for Kubernetes and the gpg key:

    1. sudo rm /etc/apt/sources.list.d/kubernetes.list
    2. sudo rm /etc/apt/keyrings/kubernetes-apt-keyring.gpg

    Then try Option #1 again.

    Hope this solution will help you to move past the install step on the control plane node.

    Regards,
    -Chris

  • Posts: 5

    @chrispokorni

    Thanks for this. I only just returned to this course today. I've tried out your suggested solution and it worked.
    I've moved on to the next Lab.

    Thanks
    oophilip

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training