Issue with calico-node on minion node
After kubeadm join
ing the minion node with the master node, I am seeing the below logs on calico-node in the minion node
2019-12-18 21:23:03.634 [INFO][10] startup.go 255: Early log level set to info 2019-12-18 21:23:03.634 [INFO][10] startup.go 271: Using NODENAME environment for node name 2019-12-18 21:23:03.634 [INFO][10] startup.go 283: Determined node name: minion-instance-1 2019-12-18 21:23:03.637 [INFO][10] k8s.go 228: Using Calico IPAM 2019-12-18 21:23:03.637 [INFO][10] startup.go 315: Checking datastore connection 2019-12-18 21:23:03.651 [INFO][10] startup.go 339: Datastore connection verified 2019-12-18 21:23:03.651 [INFO][10] startup.go 94: Datastore is ready 2019-12-18 21:23:03.660 [INFO][10] startup.go 381: Initialize BGP data 2019-12-18 21:23:03.661 [INFO][10] startup.go 583: Using autodetected IPv4 address on interface ens4: 10.128.0.4/32 2019-12-18 21:23:03.661 [INFO][10] startup.go 451: Node IPv4 changed, will check for conflicts 2019-12-18 21:23:03.665 [INFO][10] startup.go 646: No AS number configured on node resource, using global value 2019-12-18 21:23:03.665 [INFO][10] startup.go 148: Setting NetworkUnavailable to False 2019-12-18 21:23:03.669 [ERROR][10] startup.go 151: Unable to set NetworkUnavailable to False error=nodes "minion-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot patch resource "nodes/status" in API group "" at the cluster scope 2019-12-18 21:23:03.674 [INFO][10] node.go 86: Error updating Node resource error=nodes "minion-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot update resource "nodes/status" in API group "" at the cluster scope 2019-12-18 21:23:03.674 [ERROR][10] startup.go 163: Unable to set node resource configuration error=connection is unauthorized: nodes "minion-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot update resource "nodes/status" in API group "" at the cluster scope 2019-12-18 21:23:03.675 [WARNING][10] startup.go 1058: Terminating Calico node failed to start
Seems like minion node is forbidden from to update node resource. Am i missing any other steps here?
Comments
-
Oh and even though the calico node on the master is in Running status, seeing these logs in master node's calico node.
2019-12-18 21:41:44.427 [INFO][41] watchercache.go 204: Failed to perform list of current data during resync ListRoot="/calico/ipam/v2/assignment/" error=connection is unauthorized: ipamblocks.crd.projectcalico.org is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot list resource "ipamblocks" in API group "crd.projectcalico.org" at the cluster scope
0 -
I enabled http and https traffic in both my VMs with GCP console.
Also executed this commandgcloud compute firewall-rules create calico-ipip --allow 4 --network "default" --source-ranges "10.128.0.0/9"
as suggested in calico installation guide to make sure the calico traffic is allowed between containers in different nodes.
After that the status of my calico node in minion never really changed. But the master was restarted and its readiness probe is failing
Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 4m21s (x1836 over 5h10m) kubelet, master-instance-1 Readiness probe failed: calico/node is not ready: felix is not ready: readiness probe reporting 503
0 -
I tried deleting the
calico-kube-controllers
deploy as well the calico pods and re applied the calico yaml and rbac yaml.Now the logs are flipped between master and minion nodes!
In master i see this.
8 22:26:32.449 [INFO][10] startup.go 148: Setting NetworkUnavailable to False 2019-12-18 22:26:32.454 [ERROR][10] startup.go 151: Unable to set NetworkUnavailable to False error=nodes "master-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot patch resource "nodes/status" in API group "" at the cluster scope 2019-12-18 22:26:32.467 [INFO][10] node.go 86: Error updating Node resource error=nodes "master-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot update resource "nodes/status" in API group "" at the cluster scope 2019-12-18 22:26:32.467 [ERROR][10] startup.go 163: Unable to set node resource configuration error=connection is unauthorized: nodes "master-instance-1" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot update resource "nodes/status" in API group "" at the cluster scope 2019-12-18 22:26:32.467 [WARNING][10] startup.go 1058: Terminating
In minion , not seeing any errors but the pods are not in ready state.
calico-kube-controllers-6bbf58546b-4rtqm 1/1 Running 0 2m56s calico-node-vrc5p 0/1 CrashLoopBackOff 5 3m20s calico-node-zzcff 0/1 Running 3 3m33s
0 -
The calico yaml file from the course https://tinyurl.com/yb4xturm and the rbac file https://tinyurl.com/y2vqsobb are not going to work! Lot of permissions are not defined and I spent so much time trying to patch the file as I was keep getting one or other forbidden issues.
This yaml from their official documentation is complete. Use this instead - https://docs.projectcalico.org/v3.9/manifests/calico.yaml
https://docs.projectcalico.org/v2.0/getting-started/kubernetes/installation/ - Documentation on AWS and GCE installations are really helpful!
0 -
Hi @seetha33tmr, I am wondering what is so different in the way you configured your infrastructure that causes all these reported issues.
-Chris
0 -
With nodes sized accordingly, the infrastructure networking configured to fully allow traffic between your cluster nodes, and no firewalls active at the node OS level, the cluster installation scripts should be sufficient to install and run all the components including docker and calico.
Regards,
-Chris0 -
@chrispokorni I think it might be due to the rbac-kdd.yaml file downloaded in lab 2.2. The calico yaml file itself have necessary rbac roles and resources defined in it after the comment
# Source: calico/templates/rbac.yaml
. I am seeing significant differences in the resources and roles defined in calico file vs the rbac-kdd file.0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 734 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 166 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 6K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 222 LFD103 Class Forum
- 17 LFD110 Class Forum
- 34 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 110 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 113 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 18 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 118 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 50 LFS241 Class Forum
- 44 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 146 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 156 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 8 LFW111 Class Forum
- 257 LFW211 Class Forum
- 180 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- SKF201 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 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)