Comments on: How to Install and Configure Kubernetes (k8s) on Ubuntu 18.04 LTS

By: pr0708

pr0708 — Mon, 26 Apr 2021 15:25:24 +0000

fantastic… worked without any hassles!

By: Karthik

Karthik — Sun, 24 Jan 2021 16:26:17 +0000

In reply to manas. please do kubeadm reset on worker node. That should basically solve since the config was already present in the machine

By: Lionel

Lionel — Sun, 06 Oct 2019 22:37:43 +0000

In reply to manas.

1) check that you can run on the master “kubectl get nodes” if not because port6443 is closed, then run “strace -eopenat kubectl version” and retry
2) if you can no more ping the master, run “sudo ip link set cni0 down”
With this both command , I was then able to join the master from a slave.

By: doorsfan

doorsfan — Thu, 19 Sep 2019 17:45:43 +0000

flannel is broken!
use
kubectl apply -f “https://raw.githubusercontent.com/weaveworks/weave/master/prog/weave-kube/weave-daemonset-k8s-1.9.yaml”

By: Carl De Pasquale

Carl De Pasquale — Tue, 10 Sep 2019 16:20:25 +0000

Hi – I just came across the post and it is great. Everything worked fine until I tried to start a pod. I keep getting
NAME READY STATUS RESTARTS AGE
web-server-pod 0/1 ContainerCreating 0 5m17s

any ideas?

Thanks ,
Carl

By: Saikumar G

Saikumar G — Fri, 30 Aug 2019 10:15:46 +0000

While adding the slave node in the last step I got a below-mentioned error. So please let me know the way to fix it.

error execution phase preflight: couldn’t validate the identity of the API Server: abort connecting to API servers after a timeout of 5m0s

By: Nestor Alonso

Nestor Alonso — Wed, 21 Aug 2019 17:27:57 +0000

The ‘Not ready’ status on slave nodes, in my case, was due to a missing package in the nodes. Solved with apt-get install apt-transport-https. Then removed the nodes from the cluster (in master node), and joined the nodes to the cluster again from the slave nodes. A minute later, all nodes were ‘Ready’

By: Shivdas Kanade

Shivdas Kanade — Sat, 27 Jul 2019 18:09:43 +0000

Worked for me. Step by step explained. Thanks

By: Saikumar G

Saikumar G — Tue, 23 Jul 2019 09:44:45 +0000

I got following error.

[init] Using Kubernetes version: v1.15.1
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected “cgroupfs” as the Docker cgroup driver. The recommended driver is “systemd”. Please follow the guide at ‘https://kubernetes.io/docs/setup/cri/’
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR Port-10251]: Port 10251 is in use
[ERROR Port-10252]: Port 10252 is in use
[ERROR Port-10250]: Port 10250 is in use
[ERROR Port-2380]: Port 2380 is in use
[preflight] If you know what you are doing, you can make a check non-fatal with `–ignore-preflight-errors=…`

By: manas

manas — Tue, 16 Jul 2019 06:44:31 +0000

root@k8s-worker-node1:~# sudo kubeadm join 10.0.2.15:6443 –token q2r9un.l7bapq1m18wtd9ij \
> –discovery-token-ca-cert-hash sha256:72e5b3bcf18ae48d107da8a393b70b4896ca5abb8ec6609da98b4710b080ec55
[preflight] Running pre-flight checks
[WARNING IsDockerSystemdCheck]: detected “cgroupfs” as the Docker cgroup driver. The recommended driver is “systemd”. Please follow the guide at ‘https://kubernetes.io/docs/setup/cri/’

Note : While executing in slave node not going forward stuck there. Kindly anyone knows this problem?