kubectl get node error

Hello,
I'm trying to attach my node to the master and get the following error:
Kubectl on host returns error: couldn't get version/kind; json parse error: json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\""; Kind string "json:\"kind,omitempty
It looks like it's having an issue with .kube/config
.kube/config is fine on master.
Any ideas?
Thanks!
Reg
Comments
-
Hello,
Well, let's see if we can figure it out. To start, please paste the command and the output where you received the error.
When you say the config file is fine on the master, you mean that it runs without issues there? The lab does not have you copy over the file to the worker node, so if you did so did you put it in the correct place with the correct permissions, and not edit the file in any way?
What does the output of kubectl get node show?
Regards,
0 -
Hi @rdancy,
Once the worker node successfully joined the master/cluster, you should see that confirmation message at the end of the output produced by the join phase.
Then, thekubectl get node
command is expected to be run on (or against) the master node.Regards,
-Chris0 -
Here's the command I ran:
kubectl get nodes
error: error loading config file "/home/reg_dancy01/.kube/config": couldn't get version/kind; json parse error:
json: cannot unmarshal string into Go value of type struct { APIVersion string "json:\"apiVersion,omitempty\"";
Kind string "json:\"kind,omitempty\"" }Yes it runs without an issue on the master
I was following the lab, the part it says grow your cluster
0 -
The lab does not guide you to configure
kubectl
with the expected.kube/config
file on the worker node, and, as a result,kubectl
is not expected to work from the worker node.However, if you want to configure it yourself, then separately you would need to setup the
.kube/config
file on the worker node, by copying it over from the master node, and ensuring it has the same owner/permissions as found on the master node.Regards,
-Chris0 -
Hi ,
I also ran the join command before running the get nodes command:
root@instance-1:~# kubeadm join 10.128.0.3:6443 --token W0817 13:16:19.690275 --discovery-token-ca-cert-hash sha
256:0d9acb893d4ff0c34ebfd8c02644796a3924ffeca20799ca018553a7e411ce26
accepts at most 1 arg(s), received 2
To see the stack trace of this error execute with --v=5 or higher
root@instance-1:~#0 -
The value of your token does not look right. It seems to be the prefix of a Warning message, with today's date and time.
The value of the token has a different structure.
Try re-creating the token, run
kubectl reset
on the worker node, then run thekubeadm join ...
command again on the worker, with the value of the new token instead.Regards,
-Chris0 -
Hello,
From the join command you used, I notice that it does not use the alias k8smaster as the lab describes. If you skipped those steps there may be others missed. Please start with two new VMs and complete each step to configure the master and then join the worker.
Regards,
0 -
Hello
I took your advice and restarted with two new VMs. I have re-configured the master and joined the worker successfully.
Thanks for the help
Reg
0 -
Great! Glad its working.
0
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 575 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 60 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 10 LFS203 Class Forum
- 75 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
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 233 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 62 All In Program
- 62 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)