Request: Support multiple documents in KUBECONFIG

[robotrapta]

What would you like to be added:

It sure would be handy if I could put multiple YAML documents into my KUBECONFIG file, separated by ---. Each one should be able to create its own contexts, and the cluster and user references should be scoped to within that document. The context names themselves would have to share a global namespace. If there were name collisions on the context names I think it would just have to throw an error.

Why is this needed:

We work with lots of different clusters, dynamically building them for various tasks. Various tools like microk8s and eksctl are happy to generate a complete kubeconfig needed to access the cluster. But merging the kubeconfigs together is error-prone. I've seen many a smart engineer flustered for quite a while because there's a mistake in there caused by not merging them properly.

With this change it would be much easier to merge them because in almost every case you could just append --- and the generated full kubeconfig from whatever source you got it from, and the only change you'd need to make would be to the name of the context.

[k8s-ci-robot]

@robotrapta: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[eddiezane]

We've discussed this before in the form of supporting the XDG config spec. If we could do things over from the start we would make these changes but the issue is that now it would cause widespread issues for other tooling in the ecosystem.

kubernetes/enhancements#2111

/close

[k8s-ci-robot]

@eddiezane: Closing this issue.

In response to this:

We've discussed this before in the form of supporting the XDG config spec. If we could do things over from the start we would make these changes but the issue is that now it would cause widespread issues for other tooling in the ecosystem.

kubernetes/enhancements#2111

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.