The k8scp.sh script fails

lululemon33
lululemon33 Posts: 3
in LFS260 Class Forum

The following error occurs when running the k8scp.sh script:

Err:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages
404 Not Found [IP: 172.217.17.78 443]
Fetched 8993 B in 2s (4228 B/s)
Reading package lists...
E: Failed to fetch https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/by-hash/SHA256/0d7ba2a5a480b51e90c78214afbd41cb4211c23cc52c2497ebcfc3f1bb8e7e31 404 Not Found [IP: 172.217.17.78 443]
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package kubeadm
E: Unable to locate package kubelet
E: Unable to locate package kubectl
E: Unable to locate package kubelet
E: Unable to locate package kubeadm
E: Unable to locate package kubectl
E: No packages found
sudo: kubeadm: command not found
Running the steps explained at the end of the init output for you
cp: cannot stat '/etc/kubernetes/admin.conf': No such file or directory
chown: cannot access '/home/xxxxx/.kube/config': No such file or directory

Comments

  • lululemon33
    lululemon33 Posts: 3
    edited December 2023

    I get same error on the k8sWorker.sh script:

    Err:7 https://packages.cloud.google.com/apt kubernetes-xenial/main amd64 Packages
    404 Not Found [IP: 142.250.181.78 443]

    ...

    Processing triggers for man-db (2.9.1-1) ...
    kubelet set on hold.
    kubeadm set on hold.
    kubectl set on hold.

    Script finished. You now need the kubeadm join command
    from the output on the cp node

  • lululemon33
    lululemon33 Posts: 3

    Please disregard. Seems as if the mirror in my region storing the packages had intermittent issues. Ran again and all installed as expected.

Categories

Upcoming Training