search

k3d-io / k3d

Little helper to run CNCF's k3s in Docker
https://k3d.io/
MIT License
5.44k stars 462 forks source link

[HELP] Configuration of k3s cluster behind a corporate proxy with CA (on debian) #1282

Closed Wizmll closed 1 year ago

Wizmll commented 1 year ago

Question / Where do you need Help?

Scope of your Question

Wizmll commented 1 year ago

Im working on k3s on my debian machine behind a corporate proxy integrated in a firewall that uses its own self-signed certificate, I downloaded the certificate on my server and started the installation of k3s master node.

kubectl get nodes

NAME STATUS ROLES AGE VERSION dmaster3 Ready control-plane,master 4d20h v1.26.3+k3s1

Here is the output I get when I execute the command #kubectl get pods --all-namespaces, the kube-system pods remain in ContainerCreating status, and I don't know how to solve this problem

NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-7c444649cb-zq4rz 0/1 ContainerCreating 0 4d19h kube-system local-path-provisioner-5d56847996-5zcfj 0/1 ContainerCreating 0 4d19h kube-system metrics-server-7b67f64457-lpjnf 0/1 ContainerCreating 0 4d19h kube-system calico-kube-controllers-5857bf8d58-2ptdm 0/1 ContainerCreating 0 4d19h kube-system calico-node-bbrws 1/1 Running 1 (4d3h ago) 4d19h

Knowing that I already did an installation of k3s cluster and installed some services (such as Calico, kube-vip, metallb and nginx) and everything worked perfectly, but when I integrated the proxy to the infrastructure and started from 0 again, I faced this problem.

I am on debian 11.7 k3s version v1.26.3+k3s1

iwilltry42 commented 1 year ago

Following up in the discussion over here: https://github.com/k3d-io/k3d/discussions/535#discussioncomment-5925585