Unable to setup cluster on Lab 3.1
Comments
-
Hi Chris,
I attached logs from those containers who are constantly restarting ... api, controller and scheduler.
top
top - 09:57:41 up 36 min, 1 user, load average: 0.29, 0.16, 0.23
Tasks: 4 total, 0 running, 4 sleeping, 0 stopped, 0 zombie
%Cpu(s): 8.8 us, 2.4 sy, 0.0 ni, 88.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 6103588 total, 3482592 free, 333140 used, 2287856 buff/cache
KiB Swap: 0 total, 0 free, 0 used. 5506916 avail MemPID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26816 root 20 0 1856936 96232 63604 S 2.0 1.6 0:27.10 kubelet
29878 root 20 0 746656 45204 31028 S 1.0 0.7 0:19.92 kube-scheduler
25248 root 20 0 10.121g 42052 20236 S 1.0 0.7 0:22.01 etcd
23202 root 20 0 1351992 104864 50108 S 1.0 1.7 0:43.68 dockerddf -h
Filesystem Size Used Avail Use% Mounted on
udev 2.9G 0 2.9G 0% /dev
tmpfs 597M 1.1M 595M 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 19G 7.3G 11G 42% /
tmpfs 3.0G 0 3.0G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup
/dev/sda2 976M 78M 832M 9% /boot
tmpfs 597M 0 597M 0% /run/user/1000
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/07fb7deba941efdc033be06b21acb9e16370cd970afbdadfbf3687fd1a82dbec/merged
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/b4449e9b143491ef05d5958d8d7102ba73f43bc121dcdd600273e466328fcd34/merged
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/0151f780322fb4f35a2cf556b560fe13552d9a0edee9c63b75b07b10d58f77b8/merged
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/fd31cabfb8ef7dc15b148de17cd53bdbbe4286be546389376fd8cf5b086b6e18/merged
shm 64M 0 64M 0% /var/lib/docker/containers/aedf361be28fe4a9cb7e3dc5b19f8482a2c6ea89ed3fd949cf38b23d89fd390c/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/9e8931ec407841b6086cf483669d1a887bfe0c127f7f732c3298cb8387d109b1/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/e72fac362f215b647811d748c3be5d39d136a70991a0f111c9e0b551c4164733/mounts/shm
shm 64M 0 64M 0% /var/lib/docker/containers/7ca7e2c303e6ccc6fe0b014123b03a2fe2869e97f47576681fcc1a9d332cb302/mounts/shm
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/d5416c9a3486899fb5d9468453491ef14e35e72dceaeb7ffb1b2ca4e108c65d0/merged
overlay 19G 7.3G 11G 42% /var/lib/docker/overlay2/22a4483bc4a6dcb6a643670e18d3d3f5a766d5469e5822b1fd733061a104abed/merged0 -
Hi @asmoljo,
It seems that the controller and scheduler errors are timeouts caused by unsuccessful attempts to communicate with the API server. Did you see any errors during
kubeadm init
? Was the VirtualBox VM for the control-plane node provisioned new for this cluster, or has it been used for other clusters as well (you mentioned prior rke and kubespray clusters).What is the VM provisioning process you go through in VirtualBox, and what other actions do you take prior to beginning with Lab 3.1?
What is the commands history of your CLI, as you go through exercise 3.1?Regards,
-Chris0 -
@chrispokorni said:
Hi @asmoljo,It seems that the controller and scheduler errors are timeouts caused by unsuccessful attempts to communicate with the API server. Did you see any errors during
kubeadm init
? Was the VirtualBox VM for the control-plane node provisioned new for this cluster, or has it been used for other clusters as well (you mentioned prior rke and kubespray clusters).What is the VM provisioning process you go through in VirtualBox, and what other actions do you take prior to beginning with Lab 3.1?
What is the commands history of your CLI, as you go through exercise 3.1?Regards,
-ChrisHi Chris
yes i saw the errors after the init command, i have already sent them. I created a brand new server for the LFS258 course. VM creation procedure:
new, enter name, machine folder, type = Linux and version = ubuntu 64bit. RAM 4094Mb, create vdisk now, vdi disk, fixed size 20GB. set 2 CPU, set net bridged adapter, set optical drive as ubuntu server 18.04 image, and install. unfortunately I no longer have a command history.
I switched from the virtual box to the vmware workstation and for now everything works fine for me.0 -
hi friends,
As I'm following the instructions in the book, when i reached to sep 14 with this command
kubeadm init --config=kubeadm-config.yaml --upload-certs | tee kubeadm-init.out # Save output for future reviewi got this for output >>>
invalid configuration for GroupVersionKind /, Kind=: kind and apiVersion is mandatory information that must be specified
To see the stack trace of this error execute with --v=5 or higherhow can i solve this ??? what is wrong in my lab ???
0 -
I had a network/DNS problem as soon as I applied calico.yaml. DNS names were not resolved anymore. It has to do with systemd-resolved. When I 'unapplied' calico.yaml, DNS queries were fine again. I switched to Debian 10 iso Ubuntu 18.04. That worked for me. I did not feel like solving Ubuntu-problems.
0 -
Hi @RonaldHeirbaut,
Where did you setup your Ubuntu 18 VMs - in the cloud, or through a local hypervisor? What Ubuntu image did you use, and from where?
Regards,
-Chris0 -
Hi Chris, I use libvirtd (both on Centos 7 as Debian 10) and downloaded the Ubuntu image from Ubuntu. Version 18.04LTS from https://ubuntu.com/download/server#releases. Installation as simple as next-next-finish
0 -
Hi @RonaldHeirbaut,
The "next-next-finish" install implies all default configs, including networking and DNS. The networking type and how the hypervisor configures guest VMs' DNS play a key role in the behavior of your VMs during the cluster bootstrapping phase.
I typically use VirtualBox locally, and the defaults are not allowing me to bootstrap my cluster. Meaning that I have to deviate from defaults, especially when the networking is configured by the hypervisor for each VM. In VBox terms this translates to a single adapter, bridged network with promiscuous mode checked and allowing all traffic.
Regards,
-Chris0 -
@chrispokorni, the strange thing is that I can do a docker pull, dig, nslookup, ping whatsoever until I appy calico.yaml. Then it all fails. When I delete calico, everything works again.
0 -
Hello,
When you apply the calico.yaml file there are new pods created. These pods are responsible for handling the traffic inside of the node, and do so by manipulating **iptables* commands. As a result the firewall of the node is modified, which could effect all traffic.
Regards,
0
Categories
- All Categories
- 208 LFX Mentorship
- 208 LFX Mentorship: Linux Kernel
- 738 Linux Foundation IT Professional Programs
- 340 Cloud Engineer IT Professional Program
- 167 Advanced Cloud Engineer IT Professional Program
- 67 DevOps Engineer IT Professional Program
- 133 Cloud Native Developer IT Professional Program
- 123 Express Training Courses
- 123 Express Courses - Discussion Forum
- 6K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 67 LFC131 Class Forum
- 40 LFD102 Class Forum
- 223 LFD103 Class Forum
- 18 LFD110 Class Forum
- 35 LFD121 Class Forum
- 18 LFD133 Class Forum
- 7 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 4 LFD210 Class Forum
- 3 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 691 LFD259 Class Forum
- 111 LFD272 Class Forum
- 4 LFD272-JP クラス フォーラム
- 11 LFD273 Class Forum
- 119 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 2 LFS116 Class Forum
- 4 LFS118 Class Forum
- 4 LFS142 Class Forum
- 5 LFS144 Class Forum
- 4 LFS145 Class Forum
- 2 LFS146 Class Forum
- 3 LFS147 Class Forum
- 9 LFS151 Class Forum
- 2 LFS157 Class Forum
- 19 LFS158 Class Forum
- 6 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 2 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 31 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム
- 18 LFS203 Class Forum
- 120 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 51 LFS241 Class Forum
- 46 LFS242 Class Forum
- 38 LFS243 Class Forum
- 14 LFS244 Class Forum
- 2 LFS245 Class Forum
- 46 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 148 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 7 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 117 LFS260 Class Forum
- 158 LFS261 Class Forum
- 42 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 19 LFS268 Class Forum
- 30 LFS269 Class Forum
- 201 LFS272 Class Forum
- 2 LFS272-JP クラス フォーラム
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 9 LFW111 Class Forum
- 258 LFW211 Class Forum
- 181 LFW212 Class Forum
- 13 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 755 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 352 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.2K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 312 Installation
- 79 All In Program
- 79 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)