keep separate k3d kubeconfig files

[Yasinmohammed007]

Hi Team,
Please check if this already solved, Give me the link.

Problem: I want to create multiple k3d clusters and when cluster is creating i want to keep config files separately to achieve parallel tasks. by default k3d will club the 3 or n cluster configs in to Singleconfig, I dont want to use switch context, I want to create separate configs.

ex:

k3d cluster create cluster01
k3d cluster create cluster02
k3d cluster create cluster03

ConfigFile should be like
ex:

$ ls -l ~/.kube/
cluster01.yaml  cluster02.yaml cluster03.yaml

I want to use like
ex:

kubectl get pods -A --kubeconfig ~/.kube/custer01.yaml  

kubectl get pods -A --kubeconfig ~/.kube/custer02.yaml  

kubectl get pods -A --kubeconfig ~/.kube/custer03.yaml  

i was searching on k3d docs and found
k3d cluster create clustername --config /abc/test.yaml --> What is this for? i thought this will solve my problem.

root@yasin:~/.kube# k3d cluster create cluster3 --config /root/k3d_db/cluster3.yaml 
FATA[0000] Failed to stat config file /root/k3d_db/cluster3.yaml: stat /root/k3d_db/cluster3.yaml: no such file or directory 

EDIT (@iwilltry42): add code blocks for better readability

[iwilltry42]

Hi @Yasinmohammed007 , let me just go through all the parts of your question 👍

I dont want to use switch context

This is actually the "standard way" of doing things as per https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/, but it's fine, if that's not suitable for you (in any case, checkout https://github.com/ahmetb/kubectx which makes handling multiple contexts super easy).

i was searching on k3d docs

Then this is what you were searching for: https://k3d.io/usage/kubeconfig/
When you create a k3d cluster with default parameters, k3d will merge the kubeconfig from the new cluster into whatever is specified as your default kubeconfig ($HOME/.kube/config or whatever your KUBECONFIG environment variable points to).

k3d cluster create clustername --config /abc/test.yaml --> What is this for? i thought this will solve my problem.

With the --config flag, you can specify a k3d config file (see https://k3d.io/usage/configfile/ and k3d cluster create --help).

So you have at least the following to options here to achieve what you want:

1. Use a different KUBECONFIG environment variable when creating the clusters

   $ KUBECONFIG=$HOME/k3d/cluster1.yaml k3d cluster create cluster1
   ...
   $ KUBECONFIG=$HOME/k3d/cluster2.yaml k3d cluster create cluster2
   ...

2. Grab the kubeconfigs after the cluster was created:

   $ k3d cluster create cluster1
   ...
   $ k3d kubeconfig write cluster1 # creates $HOME/.k3d/kubeconfig-cluster1.yaml
   ...
   $ k3d cluster create cluster2
   ...
   $ k3d kubeconfig write cluster2 -o /tmp/cluster2.yaml` # same as before, but custom output file
   ...

[Yasinmohammed007]

Thanks @iwilltry42.