Unable to connect to the server: x509 (Lab 2.2)

Hi everyone,
yesterday I have reset kubeadm
because I could not join from master with worker node. It fails showing me this error "a Node with name and status "Ready" already exists in the cluster"
(at the moment I don't have screen about this).
Anyway, after resetting it, kubectl
throws me this error:
What is the problem?
This is the first time that I see this error.
Thank you,
Regards
Comments
-
As your font is in red, and the image grainy, I cannot make out any of the messages.
Did you reset every node? Be aware that kubeadm reset is not well used and could have some hiccups. Please try to rebuild from a fresh cluster and see if the problem persists.
Regards,
0 -
If you reset your master node
ckad-1
then keep in mind that in the process all the cluster credentials are being reset as well. As a result, if you do not update yourkubectl
credentials, you would not be able to interact with the "new" cluster. It seems you ran thek8sMaster.sh
again, and there is a chance that it did not update the/home/mary/.kube/config
file.In order to fix your cluster access, you need to run the following 2 commands:
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
At the prompt confirm the overwrite action.sudo chown $(id -u):$(id -g) $HOME/.kube/config
These commands are in the
k8sMaster.sh
script as well.Regards,
-Chris0 -
Hi @chrispokorni , @serewicz
Now I tried newly:
on master node I have reset kubeadm and executed k8sMaster.sh script, it's successuful.
The screen below is master's final outputon worker node I have reset kubeadm, I executed k8sSecond.sh script, and i tried to join with master node.
The instruction join give me this error (as mentioned previously) showed in this screen
0 -
It seems you are not following closely the lab exercise instructions. Your output shows clearly the reason for your error: you are running the
kubeadm join
command on the master/primary node. Thekubeadm join
command is expected to be executed on the worker/secondary node.Also, if the
k8sMaster.sh
script ran with its defaults, then it configured the Pod network to192.168.0.0/16
. From your output, your master node IP address is192.168.1.107
, which overlaps the Pod IP network. Perhaps you missed these configuration tips from an earlier discussion:With VirtualBox, the promiscuous mode - allow all may have to be enabled for bridged networking. Also, I see you are using the default DHCP subnet of VirtualBox, which overlaps with the Pod subnet managed by Calico in your Kubernetes cluster. This will cause DNS and routing issues sooner or later, so I'd recommend changing your VirtualBox VM subnet to prevent overlapping with the 192.168.0.0/16 Pod subnet.
Regards,
-Chris0 -
Hi,
I'm so sorry
I had that error because when I cloned the VM I didn't change host names; that's why it seemed that I run them.
Now, join instruction is executed with success and cluster is created with two nodes.Despite the procedure is successful, on worker node I had same error of this topic, i.e. "Unable to connect to the server: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: cerification error" while trying to verify candidate authority certificate "kubernetes")" when I run
kubectl get nodes
command.How I do solve this problem on worker nodes?
Thank you so much
0 -
Hello,
Typically you would not run kubectl commands on the worker nodes. In any case, the ~/.kube/config file determines both where to send the API calls as well as what keys and certs to use. I would guess that the file on your worker no longer matches the file on the master. Especially if you cloned everything, but have not cleared the file since the clone.
Regards,
0 -
Hello,
Now I resolved this problem, the ~/.kube/config files were different.
Thank you so much for your patience.
Regards
0 -
Great!
0
Categories
- All Categories
- 229 LFX Mentorship
- 229 LFX Mentorship: Linux Kernel
- 810 Linux Foundation IT Professional Programs
- 363 Cloud Engineer IT Professional Program
- 183 Advanced Cloud Engineer IT Professional Program
- 82 DevOps Engineer IT Professional Program
- 151 Cloud Native Developer IT Professional Program
- 138 Express Training Courses & Microlearning
- 138 Express Courses - Discussion Forum
- Microlearning - Discussion Forum
- 6.3K Training Courses
- 48 LFC110 Class Forum - Discontinued
- 71 LFC131 Class Forum
- 44 LFD102 Class Forum
- 228 LFD103 Class Forum
- 19 LFD110 Class Forum
- 41 LFD121 Class Forum
- 18 LFD133 Class Forum
- 8 LFD134 Class Forum
- 18 LFD137 Class Forum
- 71 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 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
- 701 LFD259 Class Forum
- 111 LFD272 Class Forum - Discontinued
- 4 LFD272-JP クラス フォーラム
- 13 LFD273 Class Forum
- 179 LFS101 Class Forum
- 1 LFS111 Class Forum
- 3 LFS112 Class Forum
- 3 LFS116 Class Forum
- 7 LFS118 Class Forum
- LFS120 Class Forum
- 9 LFS142 Class Forum
- 8 LFS144 Class Forum
- 4 LFS145 Class Forum
- 3 LFS146 Class Forum
- 2 LFS148 Class Forum
- 15 LFS151 Class Forum
- 4 LFS157 Class Forum
- 44 LFS158 Class Forum
- LFS158-JP クラス フォーラム
- 10 LFS162 Class Forum
- 2 LFS166 Class Forum
- 4 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 32 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム - Discontinued
- 19 LFS203 Class Forum
- 135 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 1 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 52 LFS241 Class Forum
- 48 LFS242 Class Forum
- 38 LFS243 Class Forum
- 15 LFS244 Class Forum
- 5 LFS245 Class Forum
- LFS246 Class Forum
- LFS248 Class Forum
- 52 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 156 LFS253 Class Forum
- 1 LFS254 Class Forum
- 1 LFS255 Class Forum
- 9 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 129 LFS260 Class Forum
- 160 LFS261 Class Forum
- 43 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 25 LFS268 Class Forum
- 32 LFS269 Class Forum
- 6 LFS270 Class Forum
- 202 LFS272 Class Forum - Discontinued
- 2 LFS272-JP クラス フォーラム
- 4 LFS147 Class Forum
- 1 LFS274 Class Forum
- 4 LFS281 Class Forum
- 12 LFW111 Class Forum
- 262 LFW211 Class Forum
- 184 LFW212 Class Forum
- 15 SKF100 Class Forum
- 1 SKF200 Class Forum
- 1 SKF201 Class Forum
- 797 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 104 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 759 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 148 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 354 Ubuntu
- 470 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 69 Mobile Computing
- 18 Android
- 38 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 374 Off Topic
- 115 Introductions
- 174 Small Talk
- 24 Study Material
- 807 Programming and Development
- 304 Kernel Development
- 485 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 987 Games
- 317 Installation
- 102 All In Program
- 102 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)