[FEATURE] export "internal" KubeConfig

[chivalryq]

Scope of your request

Hey Guys I was just using k3d to develop a tool for my Graduation Project. Here it is. https://github.com/chivalryq/mvela
Generally I want connection between clusters. In kind, I can do kind get kubeconfig --internal --name childCluster so the "Control" cluster can access this child Cluster. In the another hand, I can't access the child cluster in my shell.

I need...

• a new flag for a command (e.g. k3d cluster create --<your-flag>)?
  • which command?

k3d kubeconfig get --internal

Describe the solution you'd like

Well I didn't have enough K8s network knowledge to explain the solution, But if there's some guide I'd like to try to work on it and send a PR. :)

Thanks for your work!

[chivalryq]

I change the kubeconfig manually by substituding IP address within docker network. Now it works. Maybe this isn't elegent but it's a workaround.

[iwilltry42]

Hi @chivalryq , nice project!
So if I get it correctly, then you just need e.g. the container IP instead of 0.0.0.0 in the kubeconfig?
Actually, I shouldn't have moved this to a discussion but leave it as a feature request.. I'll take care of that.
Anyway, wouldn't you usually create a ServiceAccount and generate a separate kubeconfig for it if you want to use it in an application (instead of using the "admin kubeconfig" for this)? 🤔

[chivalryq]

Hi @iwilltry42 , Thanks for your reply. Sorry for being so late to be here. Yes, you are right how I tackle this problem. Now mvela has become another project: velad.

And yes, it would be better to create a SA and a kubeconfig when joining a managed-cluster (or sub-cluster). But as this project's multi-cluster senario is just for learning/development and testing, it would be ok to use admin kubeconfig.

I've learned a lot from building this project and thanks for your work again!