Good day, I am manually creating k3d cluster on a fresh AWS EC2 instance.
1. Installed docker, k3s, k3d.
2. Run k3d command to create cluster with 3 + 3 nodes (k3d cluster create my-cluster --servers 3 --agents 3).
Issue- when performing kubectl get nodes, I assume to list all created k3d nodes, instead, I get EC2 instance. When running k3d node ls, I clearly see all created nodes.
Question- how can I work in the k3d cluster, example, install helm charts in cluster instead of on EC2 instance. Many thanks!
05/20/2022, 8:09 AM
You're running two clusters. One is native k3s with one node running directly on the ec2 instance, and another one is in k3d with 6 nodes running in containers. You should probably decide which way you want to use k3s and just do one of them.
05/20/2022, 8:17 AM
Thanks, I would like to use k3d with 6 nodes, how do I switch to it?
05/20/2022, 8:29 AM
Uninstall k3s, and follow the link someone else posted outside this thread. The k3d docs are quite good.
05/20/2022, 8:56 AM
Uninstalled, but I am facing an issue now when running kubectl commands:
• Error from server (ServiceUnavailable): the server is currently unable to handle the request
• In docker logs for one agent (level=error msg="failed to get CA certs: <https//....../cacerts> 503 Service Unavailable")