#StackBounty: #rhel #kubernetes Kubernetes Failed to list *v1.ConfigMap: Get

Bounty: 100

I have a K8S cluster, 2 servers, 1 master, 1 worker and everything works fine.

Cluster deploy:

kubeadm init --pod-network-cidr "10.11.0.0/16" --upload-certs 

cluster:

ardc01k8s-master01.nps.local   Ready    master   41m   v1.19.2   10.10.80.1    <none>        Red Hat Enterprise Linux 8.2 (Ootpa)   4.18.0-193.19.1.el8_2.x86_64   docker://19.3.13
ardc01k8s-wrk01.nps.local      Ready    <none>   34m   v1.19.2   10.10.80.11   <none>        Red Hat Enterprise Linux 8.2 (Ootpa)   4.18.0-193.19.1.el8_2.x86_64   docker://19.3.13

When I deploy the cluster with HA (for multiple masters) Metallb fails and cant read confimaps so see the ips it can assing.

kubeadm init --control-plane-endpoint "10.10.80.10:6443" --pod-network-cidr "10.11.0.0/16" --upload-certs 

metallb controller error:

E1009 19:34:56.370850       1 reflector.go:125] pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-   78d2af792bab/tools/cache/reflector.go:98: Failed to list *v1.Service: Get https://10.12.0.1:443/api/v1/services?limit=500&resourceVersion=0: dial tcp 10.12.0.1:443: i/o timeout
I1009 19:34:56.371672       1 trace.go:81] Trace[1783558010]: "Reflector pkg/mod/k8s.io/client-go@v0.0.0-20190620085101-78d2af792bab/tools/cache/reflector.go:98 ListAndWatch" (started: 2020-10-09 19:34:26.371367929 +0000 UTC m=+1612.080726327) (total time: 30.000286335s):
Trace[1783558010]: [30.000286335s] [30.000286335s] END

metallb cant read the configmap and the services stuck in <Pending> state.

All servers are fresh RHEL installs and I made snapshots to rollback.
Any ideas?


Get this bounty!!!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.