This will require us to move to specifying KUBECONFIG every time we invoke kubectl instead of simply passing --kubeconfig since the latter does not support merging.

This will require us to move to specifying KUBECONFIG every time we invoke kubectl instead of simply passing --kubeconfig since the latter does not support merging.

This seems fine. The exact kubectl invocation is basically an implementation detail, so who really cares if it's ugly and sprawling? 🤠

Just to note that currently having multiple files listed in KUBECONFIG envvar is causing errors on kele start-up, so I'm looking forward to this fix :)
Great effort @jinnovation !

Just to note that currently having multiple files listed in KUBECONFIG envvar is causing errors on kele start-up, so I'm looking forward to this fix :)

Thanks for this. Would you mind filing a separate issue as well w/ the error symptoms that you noticed? I think these two ("kele crashes with KUBECONFIG" and "kele actually supports KUBECONFIG properly") can be related-but-separate.

Great effort @jinnovation !

Thank you for playing around with my silly side project. 😇

Hi, @jinnovation!
I think I am hitting this issue.
I get the following error:
Error caused by user's config or system: .doom.d/config.el, (error ‘/Users/nelson/.kube/config:/Users/nelson/.kube/config-teleport’ does not exist; set up kubectl properly and try again)
Let me know if you want me to provide you with any extra information. Thanks for the work you have put into creating this package!

I get the following error: Error caused by user's config or system: .doom.d/config.el, (error ‘/Users/nelson/.kube/config:/Users/nelson/.kube/config-teleport’ does not exist; set up kubectl properly and try again) Let me know if you want me to provide you with any extra information.

Definitely sounds related. I'm guessing that you set the KUBECONFIG environment variable?

Thanks for the work you have put into creating this package!

Thanks for using. 😇

kubectl config view could be useful for easily retrieving the merged configs.

> KUBECONFIG="/Users/jjin/dev/jinnovation/kele.el/tests/kubeconfig.yaml:/Users/jjin/dev/jinnovation/kele.el/tests/testdata/kubeconfig.yaml" kubectl config view 

apiVersion: v1
clusters:
- cluster:
    server: https://111.111.111.111
  name: bar
- cluster:
    proxy-url: http://proxy.example.org:3128
    server: https://123.456.789.0:9999
  name: development-cluster
- cluster:
    certificate-authority-data: DATA+OMITTED
    server: https://127.0.0.1:59798
  name: kind-kele-test-cluster0
contexts:
- context:
    cluster: development-cluster
    namespace: development-namespace
    user: development-user
  name: development
- context:
    cluster: kind-kele-test-cluster0
    namespace: kube-system
    user: kind-kele-test-cluster0
  name: kind-kele-test-cluster0
- context:
    cluster: bar
    user: foo
  name: no-namespace
current-context: kind-kele-test-cluster0
kind: Config
preferences: {}
users:
- name: development-user
  user: {}
- name: kind-kele-test-cluster0
  user:
    client-certificate-data: DATA+OMITTED
    client-key-data: DATA+OMITTED