Comments on: How to Install Kubernetes (k8s) 1.7 on CentOS 7 / RHEL 7

By: Satya

Satya — Fri, 30 Dec 2022 21:01:42 +0000

To get the weave net running on the latest k8s versions
instead of the installing the weave-net as mentioned in the post as below

kubectl apply -f “https://cloud.weave.works/k8s/net?k8s-version=$kubever”

Run

kubectl apply -f ‘https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml’

By: Satya

Satya — Fri, 30 Dec 2022 20:55:11 +0000

In reply to Yuvaraj.

Assuming you are following the exact steps and have docker installed.
Run the below and it may solve the issue
mv /etc/containerd/config.toml /etc/containerd/config.toml.bak
systemctl restart containerd
kubeadm init

By: Yuvaraj

Yuvaraj — Thu, 13 Oct 2022 13:30:05 +0000

Any input to get rid of this issue..

[init] Using Kubernetes version: v1.25.2
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
[ERROR CRI]: container runtime is not running: output: time=”2022-10-13T06:29:20-07:00″ level=fatal msg=”unable to determine runtime API version: rpc error: code = Unavailable desc = connection error: desc = \”transport: Error while dialing dial unix /var/run/containerd/containerd.sock: connect: no such file or directory\””
, error: exit status 1
[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

By: sahil

sahil — Tue, 20 Oct 2020 13:15:42 +0000

Hi,

Can you please help to get below issue.

[root@k8s-master ~]# kubectl get cs
Warning: v1 ComponentStatus is deprecated in v1.19+
NAME STATUS MESSAGE ERROR
controller-manager Unhealthy Get “http://127.0.0.1:10252/healthz”: dial tcp 127.0.0.1:10252: connect: connection refused
scheduler Unhealthy Get “http://127.0.0.1:10251/healthz”: dial tcp 127.0.0.1:10251: connect: connection refused
etcd-0 Healthy {“health”:”true”}
[root@k8s-master ~]#

By: Sneha Pakhale

Sneha Pakhale — Wed, 26 Aug 2020 11:07:00 +0000

Hi Pradeep,

Thank you for the above information.
Can you please give the steps for adding windows node to Kubernetes cluster.

By: Uday

Uday — Sun, 23 Aug 2020 14:44:10 +0000

Thank you very much for the detailed instructions and explanation. Configured successfully

By: Sfa

Sfa — Thu, 23 Jul 2020 18:46:10 +0000

Thank you. I love how you broke up the setup to master and worker nodes; something I struggled to find on the net.

By: Grayman

Grayman — Fri, 05 Jun 2020 23:00:15 +0000

In reply to Ritesh.

Even I have the similar issues; don’t know how to make it work yet…there should be very specific reason for it to not to come READY state..

[root@etcd2 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
etcd1.hdp3.cisco.com Ready 48m v1.18.3
etcd2.hdp3.cisco.com NotReady master 136m v1.18.3
etcd3.hdp3.cisco.com Ready 48m v1.18.3

[root@etcd2 ~]# kubectl get pods –all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-66bff467f8-25pg4 1/1 Running 0 133m
kube-system coredns-66bff467f8-r64mg 1/1 Running 0 133m
kube-system etcd-etcd2.hdp3.cisco.com 1/1 Running 1 133m
kube-system kube-apiserver-etcd2.hdp3.cisco.com 1/1 Running 1 133m
kube-system kube-controller-manager-etcd2.hdp3.cisco.com 1/1 Running 1 133m
kube-system kube-proxy-9vm77 1/1 Running 0 45m
kube-system kube-proxy-pk2bh 1/1 Running 1 133m
kube-system kube-proxy-z2tv7 1/1 Running 0 46m
kube-system kube-scheduler-etcd2.hdp3.cisco.com 1/1 Running 1 133m
kube-system weave-net-6cnmh 2/2 Running 0 25m
kube-system weave-net-h4gr5 2/2 Running 0 25m
kube-system weave-net-tb4td 2/2 Running 0 25m

By: izzy

izzy — Mon, 25 May 2020 18:34:03 +0000

Hi Vishal,

Did you manage to get an answer why you was getting this error? Any idea how to resolve it?

By: izzy

izzy — Sat, 16 May 2020 00:27:57 +0000

In reply to izzy. solved this by forcing the node name. Past the kubeadm join token and at the end append --node-name