0

ITNOA

I install K8s control plane node with kubeadm init with custom IP for control plane endpoint address and custom IP for API server address

I try to install cilium as network plugin for K8s

I run below command from cilium installation page

curl -L --remote-name-all https://github.com/cilium/cilium-cli/releases/latest/download/cilium-linux-amd64.tar.gz{,.sha256sum}
sha256sum --check cilium-linux-amd64.tar.gz.sha256sum
sudo tar xzvfC cilium-linux-amd64.tar.gz /usr/local/bin
rm cilium-linux-amd64.tar.gz{,.sha256sum}

After install cilium CLI successfully

I try to install cilium with cilium install command, and I see below log

ℹ️  using Cilium version "v1.10.4"
🔮 Auto-detected cluster name: kubernetes
🔮 Auto-detected IPAM mode: cluster-pool
🔑 Generating CA...
2021/10/22 19:21:27 [INFO] generate received request
2021/10/22 19:21:27 [INFO] received CSR
2021/10/22 19:21:27 [INFO] generating key: ecdsa-256
2021/10/22 19:21:27 [INFO] encoded CSR
2021/10/22 19:21:27 [INFO] signed certificate with serial number 671304957005340742746064183282868481026201707487
🔑 Generating certificates for Hubble...
2021/10/22 19:21:27 [INFO] generate received request
2021/10/22 19:21:27 [INFO] received CSR
2021/10/22 19:21:27 [INFO] generating key: ecdsa-256
2021/10/22 19:21:27 [INFO] encoded CSR
2021/10/22 19:21:27 [INFO] signed certificate with serial number 383132851208063652055811547838801072394063240314
🚀 Creating Service accounts...
🚀 Creating Cluster roles...
🚀 Creating ConfigMap for Cilium version 1.10.4...
🚀 Creating Agent DaemonSet...
🚀 Creating Operator Deployment...
⌛ Waiting for Cilium to be installed...
⌛ Waiting for Cilium to become ready before restarting unmanaged pods...
↩️ Rolling back installation...

Error: Unable to install Cilium: interrupted while waiting for daemonset cilium to become ready: context deadline exceeded

As you can see in last line I got error message

Unable to install Cilium: interrupted while waiting for daemonset cilium to become ready: context deadline exceeded

My OS is: Ubuntu 20.04.3

My K8s version is: 1.22.2

How to resolve this problem?

Update:

I think systemd 245 breaks cilium pod to out-of-node traffic GitHub issue maybe can help to resolve this issue, but I cannot resolve this issue with that

thanks

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.