Got stuck on Chapter 3 Installation and Configuration on Node

I got stuck when running the kubeadm and I believe I have followed the step by step instruction. Any feedback would be appriciated.
Operating System: CentOS 7.5
Oracle VM Virtual Box:
- Bridge network, allow all promiscuous mode
- 2 vCPU
- Base memory 4096M
- OS Disk 15G
- DHCP with static IP 192.168.0.31, DNS Server 192.168.0.24
Chapter 3 Installation and Configuration on Node
Steps to reproduce on Node:
1. su - root
2. yum update && yum upgrade –y
3. yum install docker
- vi /etc/yum.repos.d/kubernetes.repo
[Kubernetes_Repository]
name=Kubernetes
baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg https://packages.cloud.google.com/yum/doc/yum-key.gpg - yum update
yum install kubeadm kubelet kubectl –y
wget https://docs.projectcalico.org/v3.3/getting-started/kubernetes/installation/hosted/rbac-kdd.yaml
wget https://docs.projectcalico.org/v3.3/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.7/calico.yamlless calico.yaml
systemctl enable docker.service
- systemctl enable kubelet.service
- systemctl stop firewalld
- swapoff –a
- kubeadm init --kubernetes-version 1.15.1 --pod-network-cidr 192.168.0.0/16 | tee kubeadm-init.out
Error Result:
[kubelet-check] Initial timeout of 40s passed.
Error execution phase wait-control-plane: couldn’t initialize a Kubernetes cluster
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:
- The kubelet is not running
The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
If you are on a system-powered system, you can try to troubleshoot the error with the following commands :‘systemctl status kubelet’
‘journalctl –xeu kubelet’
Additionally, a control plane component may have crashed or exited when started by the container runtime. To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker .
Here is one example how you may list all Kubernetes containers running in docker:‘docker ps –a | grep kube | grep –v pause’
Once you have found the failing container, you can inspect its logs with:‘docker logs CONTAINERID”
When checking kubelet.service, it says “node server031.whiteopen.com” not found but the kubelet is on active(running) state.
When running this command “kubectl –n kube-system get cm kubeadm-config –oyamlkubectl
The result was “The connection to the server localhost:8080 was refused – did you specify the right host or port?”
Comments
-
Hi,
Please read carefully all the notes and instructions in the Overview section. They provide important VM sizing details for both cloud and local installations. From your notes above, it seems your master node may not be sized accordingly.
When setting up Virtual Box VMs, these were the steps which worked for me (this was a while back, but I assume they still work the same):
1. Create 2 VMs (inspect lab exercise for sizing details)
2. Each VM with 1 NIC adapter - Bridged, Promiscuous mode: Allow All
3. Install guest OS (Ubuntu 16.04 LTS in my case) and virtualbox guest additions
4. Check ufw status, it should be inactive (or any firewall at the guest OS level)
5. Disable the swap partition
6. Verify VMs' full access to the internet and between each other via nc (netcat)
7. Run the installation steps provided in the lab to install docker and kubernetes on each VMsThe lab exercises in their current format require Kubernetes v1.14.1. Download v1.14.1 (instead of latest, as it seems you did based on your notes above) and bootstrap your master with
kubeadm init --kubernetes-version 1.14.1 ...
.The kubelet service error seems to be related to the DNS configuration of your virtual environment, which may be work-related?
The kubectl command above seems a little off, maybe due to a copy/paste issue, but, kubectl will not run until you finish the master's setup process and fully configure kubectl with necessary endpoint, keys, certs to access the cluster control plane. By attempting to run it so early in the process will produce errors such as yours.
I hope this helps.
If all else fails, just spin up 2 Ubuntu 16 LTS VMs and follow the exercises as they are presented in the lab manual, or sign up for the free 1 year trial of GCP and spin up 2 GCE Ubuntu instances in the cloud.Regards,
-Chris0 -
Hello Chris,
I see. So i need to use the Kubernetes v.1.14.1 instead of the latest?
I was trying to set the first node and for the requirement it said that i was ready for the course when i ran the ready-for.sh.Firewall was already inactive and swap was off. But what do you mean by "The kubelet service error seems to be related to the
DNS configuration of your virtual environment, which may be work-related?". Sorry, i am a beginner and does not have enough knowledge about network but the network can ping google or yahoo.
May i know how to properly configure the network in my case? I want to use static IP which is 192.168.0.31 and my DNS server is 192.168.0.24.
For the kubectl, i found that command from some forums that i have surfed to debug the errors.
I will try the installation from the start, and using Kubernetes v.1.14.1.Thank you for the information and reply.
If it still does not work, i will try using the images that prepared by LF or your recommendations.Regards,
Neirkate0 -
Hello,
The ready-for.sh script is used to make sure the non-kubernetes software is present, it does not configure the cluster itself. If using an Ubuntu instance you should be able to follow the commands as written and find success. Please note the overview to the installation lab mentions other considerations such as opening all firewall ports.
I encourage you to read the full lab document, not just the commands to type.
Regards,
0 -
Hello,
Yes, i know the ready-for.sh script is to check for the environment requirements only, and it was my first step after installing CentOS 7.
I have read the lab documentations from Lab 1 - Lab 3 since i was doing it step by step. For the firewall, i chose to stop the firewalld service so there will be no firewall. I've configured the sudo for the system too.I'll try with Ubuntu then instead of CentOS 7.
Thanks.
Regards,
Neirkate0
Categories
- All Categories
- 49 LFX Mentorship
- 102 LFX Mentorship: Linux Kernel
- 550 Linux Foundation Boot Camps
- 294 Cloud Engineer Boot Camp
- 118 Advanced Cloud Engineer Boot Camp
- 52 DevOps Engineer Boot Camp
- 53 Cloud Native Developer Boot Camp
- 4 Express Training Courses
- 4 Express Courses - Discussion Forum
- 1.9K Training Courses
- 18 LFC110 Class Forum
- 6 LFC131 Class Forum
- 24 LFD102 Class Forum
- 150 LFD103 Class Forum
- 17 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 596 LFD259 Class Forum
- 102 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 3 LFS203 Class Forum
- 69 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 33 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 139 LFS253 Class Forum
- 1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 92 LFS260 Class Forum
- 129 LFS261 Class Forum
- 32 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS281 Class Forum
- 220 LFW211 Class Forum
- 166 LFW212 Class Forum
- SKF100 Class Forum
- 901 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 761 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 141 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 356 Ubuntu
- 476 Linux System Administration
- 41 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 66 Mobile Computing
- 23 Android
- 29 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 536 Off Topic
- 131 Introductions
- 216 Small Talk
- 21 Study Material
- 816 Programming and Development
- 275 Kernel Development
- 507 Software Development
- 927 Software
- 260 Applications
- 183 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 59 All In Program
- 59 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)