Following the k8s install docs yields errors

[danbachar]

Following the doc here, I get the following errors on a fresh install of Ubuntu 22.10:

...
Err:6 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
Reading package lists... Done
W: GPG error: https://packages.cloud.google.com/apt kubernetes-xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B53DC80D13EDEF05
E: The repository 'https://apt.kubernetes.io kubernetes-xenial 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.
 installing kubectl kubeadm kubelet...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

No apt package "kubeadm", but there is a snap with that name.
Try "snap install kubeadm"


No apt package "kubectl", but there is a snap with that name.
Try "snap install kubectl"


No apt package "kubelet", but there is a snap with that name.
Try "snap install kubelet"

E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl

[jasonnovichRunAI]

@danbachar Thank you for your help in finding issues in our documentation. We have assigned this issue for follow up and we will do our best to get this corrected.

[danbachar]

I have my own setup script and I think I've identified the culprit. To add the kubernetes apt repo you're running echo "deb [signed-by=/usr/share/keyrings/kubernetes-archive-keyring.gpg] https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list. My script runs echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list, and it works. I ran your script and got to the error, then ran the aforementioned lined and can now install the kubernetes components. Should I create a PR for this?

[jasonnovichRunAI]

Yes, please create a PR. I am currently working on a contribution guideline file, so at the moment, please issue the PR for the v2.13 branch. We will need to check to see if this is applicable to previous versions as well.