Lab 1C(a) - Running Fluentd in a Kubernetes Environment

superman1

There are two issues with install Kubernetes in Linux.

1. There is an error: curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
   Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
   OK

2. echo "deb http://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee -a /etc/apt/sources.list.d/kubernetes.list
   Hit:7 https://packages.fluentbit.io/ubuntu/noble noble InRelease
   Err:8 https://packages.cloud.google.com/apt kubernetes-xenial Release
   404 Not Found [IP: 173.194.194.102 443]
   Reading package lists... Done
   E: The repository 'http://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file.
   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.

I would greatly appreciate the help. A lot of the reference points and program version are out of date. Please, help.

Is there something else I can do in the mean time?

superman1

There is no way to get Kubernetes to work based on the information from the document that Linux Foundation has provided. I am running into so many errors. I have to troubleshoot so much.

I even got to a point to do this command:
kubectl cluster-info

I get connection refused.

The connection to the server 10.1.0.1:6443 was refused - did you specify the right host or port?

I am using a Linux VM Ubuntu. I use SSH to connect to it from home. Please help me this is frustrating that half of information is out of date from this course.

chrispokorni

Hi @superman1,

I compiled a set of instructions to install Kubernetes and configure the runtime on an Ubuntu system, however, due to restrictions of this forum platform, the instructions set is blocked.

You can retrieve them from this gist instead.
It intends to replace steps 2a, 2b, and 2c of Lab 1C(a).
You can run the shell script as is, or manually execute select instructions.

Let me know if you encounter any issues.

Regards,
-Chris

superman1

Running into issue with docker.service not stopping:

I used the command:

sudo systemctl stop docker

Results:

Stopping 'docker.service', but its triggering units are still active:
docker.socket

Side note:
I love the information you provided and if you have others to help me setup the other labs. I would greatly appreciate it.

chrispokorni

Hi @superman1,

Ah... an error on my part... Forgot about docker.socket, it needs to be stopped as well, otherwise it keeps bringing up the docker.service.
sudo systemctl stop docker.socket

Check the status of the docker.service and docker.socket to ensure they are both stopped
sudo systemctl status docker.service
sudo systemctl status docker.socket

Regards,
-Chris

superman1

Those commands worked!!

When I get to this step of the command:

I use this command:
sudo sed -e 's/SystemdCgroup = false/SystemdCgroup = true/g' -i /etc/containerd/config.toml

Response is:
sed: can't read /etc/containerd/config.toml: No such file or directory

Should I be doing the step from the PDF:
"We will not be using anything from the existing configuration file. Simply replace the existing contents with the following."

sudo vi /etc/containerd/config.toml
[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc] [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
SystemdCgroup = true

superman1

It appears adding the new file worked.

But now I get pre-flight check errors:

Used command:

sudo kubeadm init --kubernetes-version "1.31.1" --pod-network-cidr "10.244.0.0/16" --cri-socket "unix:///run/containerd/containerd.sock"

Results Error:

[init] Using Kubernetes version: v1.31.1
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
[ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
[ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
[ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
[ERROR Port-10250]: Port 10250 is in use
[ERROR DirAvailable--var-lib-etcd]: /var/lib/etcd is not empty
[preflight] If you know what you are doing, you can make a check non-fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with --v=5 or higher

chrispokorni

Hi @superman1,

Perhaps adding sudo in front of the tee command should do the trick.
sudo containerd config default | sudo tee /etc/containerd/config.toml

Regards,
-Chris

chrispokorni

Hi @superman1,

Running init several times in a row does not help. This is why you see those errors.
Prior to running init, run the following command sudo kubeadm reset and confirm your intent to "reset" when prompted.

Regards,
-Chris

superman1

@chrispokorni that sudo kubeadm reset worked.

When I do the following command:

kubectl taint nodes --all node-role.kubernetes.io/control-plane-

Respond Error:

E1011 01:28:24.925994 445345 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"https://10.1.0.5:6443/api?timeout=32s\": dial tcp 10.1.0.5:6443: connect: connection refused"

I'm not understanding the error. Could you help me with this?

chrispokorni

Hi @superman1,

Perhaps the $HOME/.kube/config manifest needs to be updated with the admin credentials generated by latest init.

Regards,
-Chris