Lab 3.4. Deploy a Simple Application

marcossantos

Hello goodnight!

I'm facing some issues, I'm running my lab on VMs locally.

In exercise 3.4: Deploy A Simple Application

we created an Nginx deploy but it is not in Ready status.

Another problem is that the coredns are never in the running state, just ContainerCreating, I already delete the pods and they always stay in the same state.

Events of CoreDNS:

Warning FailedScheduling 56m (x2 over 61m) default-scheduler 0/4 nodes are available: 4 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/4 nodes are available: 4 Preemption is not helpful for scheduling..
Warning FailedCreatePodSandBox 52m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "049a481afb0b9c9b8220c91f12a946765ec2307fef22d8a2352b8d2af1907a3e": plugin type="cilium-cni" failed (add): unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http://localhost/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?

I have cilium cli instaled on my machine.

Unable to detect Cilium version, assuming v1.14.5 for connectivity tests: unable to parse cilium version on pod "cilium-7c76g": unable to parse cilium version on pod "cilium-7c76g": Version string empty
connectivity test failed: failed to fetch cilium runtime config: error with exec request (pod=kube-system/cilium-7c76g, container=cilium-agent): command terminated with exit code 1
root@masternode:/home/marcos# cilium install
ℹ️ Using Cilium version 1.14.5
🔮 Auto-detected cluster name: kubernetes
🔮 Auto-detected kube-proxy has been installed

Error: Unable to install Cilium: Unable to continue with install: ServiceAccount "cilium" in namespace "kube-system" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "cilium"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "kube-system"

Can you help resolve this core DNS issue?

I tested this but it didn't work.
https://github.com/cilium/hubble/issues/238

Scheduled 2m34s default-scheduler Successfully assigned kube-system/coredns-787d4945fb-h5btt to workernode02
Warning FailedCreatePodSandBox 104s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "586a2311b1911a2de21fe33494928296976b2b9514b95b5d93b77c9464f61f52": plugin type="cilium-cni" failed (add): unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http://localhost/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?
Warning FailedCreatePodSandBox 42s kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "55072a134f11c47865118df20ccb6983b747f18a7d2eaccfef2334b9d800e621": plugin type="cilium-cni" failed (add): unable to connect to Cilium daemon: failed to create cilium agent client after 30.000000 seconds timeout: Get "http://localhost/v1/config": dial unix /var/run/cilium/cilium.sock: connect: no such file or directory
Is the agent running?
root@masternode:/home/marcos#

marcossantos

I revisited the site https://docs.cilium.io/en/stable/installation/k8s-install-kubeadm/

To try to install cilium again but it complained that the resource was already installed in the kube-system namespace

Basically, after deleting everything related to Cilium, the core DNS and deployment were running.