LFD259 - Labs exercises and nodes preparation

Hi all,
I'm facing some issues during CP/WORKER nodes configuration.
Steps accomplished without issues:
- 2 KVM VMs created on my PC with 2 vCPUs and 4096MB of RAM;
- Ubuntu 18.04.5 LTS installed;
- SWAP commented in /etc/fstab;
- TAR downloaded (LFD259_V2021-06-15_SOLUTIONS.tar.xz) without issues;
Executing k8scp.sh, all updates are completed successfully, but KUBERNETES "cp" node initialization fails.
Investigating into the journal I've found this error:
"Jun 16 14:58:16 cp kernel: overlayfs: unrecognized mount option "metacopy=on" or missing value"
I've solved this issue removing "metacopy=on" from /etc/containers/storage.conf, but is this solution the right one?
After reboot of KUBERNETES starts without any issue:
[email protected]:~$ kubectl get node
NAME STATUS ROLES AGE VERSION
cp Ready <none> 27m v1.21.1
CONTAINER STATE NAME
a64cce5302538 Running kube-controller-manager
c181c00f10f46 Running kube-apiserver
04c53077ff511 Running kube-scheduler
baf85e1387be7 Running etcd
I can see PODS but no ROLES are configured for node "cp".
Is something else missing?
Thanks to all in advance.
Massimiliano
Comments
-
Another solution suggested a Kernel update to 5.4. However, I have not heard how this may impact (if at all) the rest of the lab exercises.
Regards,
-Chris0 -
Thanks alot Chris.
I'm trying to go on with that workaround, but still facing another issue.I've seen an ugly stacktrace into kube-scheduler container logs:
W0620 11:34:07.572449 1 requestheader_controller.go:193] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
W0620 11:34:07.572579 1 authentication.go:336] Error looking up in-cluster authentication configuration: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
W0620 11:34:07.572651 1 authentication.go:337] Continuing without authentication configuration. This may treat all requests as anonymous.
W0620 11:34:07.572683 1 authentication.go:338] To require authentication configuration lookup to succeed, set --authentication-tolerate-lookup-failure=false
... ... stack trace ... ...
E0620 11:34:11.369883 1 reflector.go:138] k8s.io/apiserver/pkg/server/dynamiccertificates/configmap_cafile_content.go:206: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot list resource "configmaps" in API group "" in the namespace "kube-system"
I0620 11:34:15.348486 1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0620 11:34:15.749621 1 leaderelection.go:243] attempting to acquire leader lease kube-system/kube-scheduler...
I0620 11:34:15.772647 1 leaderelection.go:253] successfully acquired lease kube-system/kube-schedulerkube-scheduler container is running, but I think, looking at the log that something went wrong.
Some ideas?
Thanks in advance
0 -
Hi @chrispokorni,
thanks alot.
I'm trying to go on using that workaround.I'm still facing another issue with kube-scheduler running but LOGS show a stacktrace with lots of errors:
I0620 11:34:02.789645 1 serving.go:347] Generated self-signed cert in-memory
W0620 11:34:07.572449 1 requestheader_controller.go:193] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
W0620 11:34:07.572579 1 authentication.go:336] Error looking up in-cluster authentication configuration: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot get resource "configmaps" in API group "" in the namespace "kube-system"
W0620 11:34:07.572651 1 authentication.go:337] Continuing without authentication configuration. This may treat all requests as anonymous.
W0620 11:34:07.572683 1 authentication.go:338] To require authentication configuration lookup to succeed, set --authentication-tolerate-lookup-failure=false
I0620 11:34:07.611719 1 secure_serving.go:197] Serving securely on 127.0.0.1:10259
I0620 11:34:07.613258 1 configmap_cafile_content.go:202] Starting client-ca::kube-system::extension-apiserver-authentication::client-ca-file
... ... ... ...
E0620 11:34:10.740321 1 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.CSINode: failed to list *v1.CSINode: csinodes.storage.k8s.io is forbidden: User "system:kube-scheduler" cannot list resource "csinodes" in API group "storage.k8s.io" at the cluster scope
E0620 11:34:10.943746 1 reflector.go:138] k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.StatefulSet: failed to list *v1.StatefulSet: statefulsets.apps is forbidden: User "system:kube-scheduler" cannot list resource "statefulsets" in API group "apps" at the cluster scope
E0620 11:34:11.369883 1 reflector.go:138] k8s.io/apiserver/pkg/server/dynamiccertificates/configmap_cafile_content.go:206: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot list resource "configmaps" in API group "" in the namespace "kube-system"
I0620 11:34:15.348486 1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0620 11:34:15.749621 1 leaderelection.go:243] attempting to acquire leader lease kube-system/kube-scheduler...
I0620 11:34:15.772647 1 leaderelection.go:253] successfully acquired lease kube-system/kube-schedulerI think it's failed.
Ciould you help me to understand?
Thanks.
Max
0 -
Hello,
If I read the above information correctly your nodes each have 4G of memory. If the control panel does not have enough resources odd things happen. What happens if you build the cp with 2cpu/8G?
Regards,
0 -
Hi @serewicz ,
thanks for your suggestion.
Yes you are right, WEIRD things happen.Now "kube-scheduler" starts well, even if WARNING is present:
I0620 15:33:58.425160 1 serving.go:347] Generated self-signed cert in-memory W0620 15:34:02.988872 1 requestheader_controller.go:193] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLEBINDING_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA' W0620 15:34:02.988951 1 authentication.go:336] Error looking up in-cluster authentication configuration: configmaps "extension-apiserver-authentication" is forbidden: User "system:kube-scheduler" cannot get resource "configmaps" in API group "" in the namespace "kube-system" W0620 15:34:02.988969 1 authentication.go:337] Continuing without authentication configuration. This may treat all requests as anonymous. W0620 15:34:02.988979 1 authentication.go:338] To require authentication configuration lookup to succeed, set --authentication-tolerate-lookup-failure=false I0620 15:34:03.052332 1 secure_serving.go:197] Serving securely on 127.0.0.1:10259 I0620 15:34:03.052438 1 configmap_cafile_content.go:202] Starting client-ca::kube-system::extension-apiserver-authentication::client-ca-file I0620 15:34:03.052461 1 shared_informer.go:240] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file I0620 15:34:03.052485 1 tlsconfig.go:240] Starting DynamicServingCertificateController I0620 15:34:03.152922 1 shared_informer.go:247] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file I0620 15:34:03.153118 1 leaderelection.go:243] attempting to acquire leader lease kube-system/kube-scheduler... I0620 15:34:19.672580 1 leaderelection.go:253] successfully acquired lease kube-system/kube-scheduler
The last ISSUE I'm facing is "calico-node" doesn't startup cause:
2021-06-20 15:47:17.285 [INFO][8] startup/startup.go 465: Hit error connecting to datastore - retry error=Get "https://10.96.0.1:443/api/v1/nodes/foo": dial tcp 10.96.0.1:443: connect: connection refused
But I can see ClusterIP service up:
[email protected]:~/LFD259/SOLUTIONS/s_02$ kubectl get services -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 19m <none>
Telnet on that IP:PORT succeed.
VM network config is the following (I hope it's as expected):... ... 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:06:0e:16 brd ff:ff:ff:ff:ff:ff inet 10.2.0.49/24 brd 10.2.0.255 scope global dynamic ens3 valid_lft 2485sec preferred_lft 2485sec inet6 fe80::5054:ff:fe06:e16/64 scope link valid_lft forever preferred_lft forever 3: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether aa:03:2c:42:14:7d brd ff:ff:ff:ff:ff:ff inet 10.85.0.1/16 brd 10.85.255.255 scope global cni0 valid_lft forever preferred_lft forever inet6 1100:200::1/24 scope global valid_lft forever preferred_lft forever inet6 fe80::a803:2cff:fe42:147d/64 scope link valid_lft forever preferred_lft forever ... ...
I can add:
[email protected]:~/LFD259/SOLUTIONS/s_02$ kubectl describe svc kubernetes Name: kubernetes Namespace: default Labels: component=apiserver provider=kubernetes Annotations: <none> Selector: <none> Type: ClusterIP IP Family Policy: SingleStack IP Families: IPv4 IP: 10.96.0.1 IPs: 10.96.0.1 Port: https 443/TCP TargetPort: 6443/TCP Endpoints: 10.2.0.49:6443 Session Affinity: None Events: <none>
0 -
Hi @serewicz,
SOLVED.
Thanks, thanks, thanks, thanks and sorry to have not followed your guidelines from the first start.0
Categories
- 8.8K All Categories
- 12 LFX Mentorship
- 65 LFX Mentorship: Linux Kernel
- 356 Linux Foundation Boot Camps
- 226 Cloud Engineer Boot Camp
- 69 Advanced Cloud Engineer Boot Camp
- 23 DevOps Engineer Boot Camp
- 5 Cloud Native Developer Boot Camp
- 724 Training Courses
- 14 LFC110 Class Forum
- 16 LFD102 Class Forum
- 96 LFD103 Class Forum
- 2 LFD121 Class Forum
- 55 LFD201 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 14 LFD254 Class Forum
- 420 LFD259 Class Forum
- 78 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 15 LFS200 Class Forum
- 683 LFS201 Class Forum
- LFS201-JP クラス フォーラム
- 271 LFS211 Class Forum
- 50 LFS216 Class Forum
- 23 LFS241 Class Forum
- 26 LFS242 Class Forum
- 18 LFS243 Class Forum
- 4 LFS244 Class Forum
- 7 LFS250 Class Forum
- LFS250-JP クラス フォーラム
- 103 LFS253 Class Forum
- 753 LFS258 Class Forum
- 7 LFS258-JP クラス フォーラム
- 48 LFS260 Class Forum
- 74 LFS261 Class Forum
- 6 LFS262 Class Forum
- 76 LFS263 Class Forum
- 14 LFS264 Class Forum
- 10 LFS266 Class Forum
- 8 LFS267 Class Forum
- 8 LFS268 Class Forum
- 4 LFS269 Class Forum
- 173 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 184 LFW211 Class Forum
- 99 LFW212 Class Forum
- 875 Hardware
- 204 Drivers
- 74 I/O Devices
- 43 Monitors
- 115 Multimedia
- 204 Networking
- 98 Printers & Scanners
- 82 Storage
- 716 Linux Distributions
- 78 Debian
- 64 Fedora
- 12 Linux Mint
- 13 Mageia
- 22 openSUSE
- 125 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 344 Ubuntu
- 445 Linux System Administration
- 33 Cloud Computing
- 63 Command Line/Scripting
- Github systems admin projects
- 88 Linux Security
- 73 Network Management
- 105 System Management
- 45 Web Management
- 50 Mobile Computing
- 18 Android
- 19 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 499 Off Topic
- 119 Introductions
- 193 Small Talk
- 19 Study Material
- 742 Programming and Development
- 237 Kernel Development
- 471 Software Development
- 898 Software
- 244 Applications
- 178 Command Line
- 2 Compiling/Installing
- 72 Games
- 313 Installation
- 19 All In Program
- 19 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)