LFS258 updated to k8s 1.31.1 and Ubuntu 24.04 (9/30/2024)

fcioanca

Hi,

Kubernetes Administration (LFS258) has been updated to Kubernetes v1.31.1 and Ubuntu 24.04. We have updated the scripts, YAMLs, and lab content to align with the new version. Course lectures have received some minor updates as well.

To ensure you have access to the latest course version, please clear your cache.

Regards,
Flavia
Linux Foundation Education

PetroKazmirchuk

LFS258-labs_V2024-09-30.pdf, chapter 3 step 21:
I suppose this option is wrong:
--node-name=cp
and it produces:
[WARNING Hostname]: hostname "cp" could not be reached
instead it should say:
--node-name=k8scp

chrispokorni

Hi @PetroKazmirchuk,

If you pay close attention to the training guide, and the warning produced by the command, you can easily see that cp is the actual hostname of the control plane node. In the context of the lab guide, the command is correct. While using the k8scp alias works, setting the node name as such during the init phase introduces inconsistencies in your environment and eventually conflicts in later lab exercises.

Make sure to use the control plane hostname of your Kubernetes cluster, or simply cp if it is included in the /etc/hosts file together with the k8scp alias.

Regards,
-Chris

PetroKazmirchuk

understood, many thanks for your quick reply!

admusin

Hello TLF Team,

I'm a bit confused.
Currently I'm going through the LFS258 and I'm in the beginning part at Lab 3.1. Install Kubernetes.

Step 14, pertaining to downloading the GPG key for the K8s repo reads:

root@cp: ̃# curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.29/deb/Release.key \
| sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg

So according to the above we'd be working with K8s v1.29.

Step 15, pertaining to adding the Deb repository for which we presumably added the GPG key in the previous step, reads:

root@cp: ̃# echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] \
https://pkgs.k8s.io/core:/stable:/v1.30/deb/ /" \
| sudo tee /etc/apt/sources.list.d/kubernetes.list

Unless I read this wrong, the above would imply that we should actually install K8s v1.30.
Not only that but since in Step 14 we added the GPG key for v1.29 and now we're adding the repo for v1.30, won't that generate some errors when trying to do an apt update?

Also the instructions in Steps 9-10 of this lab guide, still mention the the commands below which as I understand apply for K8s v1.29 and older (in the official K8s documentation for preparing the installation of a container runtime, they seem to have disappeared starting with v1.30):

root@cp: ̃# modprobe overlay
root@cp: ̃# modprobe br_netfilter
...
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1

OTOH, this post announces that the course has been updated to use K8s v1.31.

I guess my question is:
With which version of K8s are we supposed to follow along for the remainder of the course?

Thank you in advance.

Best regards,
Adrian

chrispokorni

Hi @admusin,

Thanks for pointing out the typo... that is the /v1.29/ in the command retrieving the gpg key. For consistency, it should be /v1.30/, however, the gpg key remains the same for all releases. Therefore, what matters most is the Kubernetes package you download, which is the correct version v1.30 for Lab 3. With a little patience, once you reach Lab 4, v1.31 will be revealed

Regards,
-Chris

admusin

Hi Chris,

Thanks for the clarification.
Reading further through the lab PDF I could see that indeed the v1.30 was being installed so I suspected as much.

But thanks for confirming it and for pointing out the reason we're starting with v1.30 and not the latest.

Best regards,
Adrian