Add option to specify kubeconfig when creating kind clusters about kind

[BenTheElder]

We've also debated just writing to this in the first place like most deployers, cc @Katharine @munnerz @justinsb

We can definitely add a --kubeconfig as well
/assign

[font]

We've also debated just writing to this in the first place like most deployers

Yeah I think that would be consistent with most other tools. Then the --kubeconfig option could be used to implement the existing default behavior i.e. separate kind-config-<name> files.

[BenTheElder]

/kind feature
/priority important-soon

[BenTheElder]

Yeah, I just dislike that this seems racy (writing to the shared file) but it seems to be done by like, every other deployer in existence, so I guess that's OK.

We'd also have to consider if deleting the cluster should remove those then, since before we were going to just implement deleting the file.

[BenTheElder]

#112 seems less trivial than initially expected, so far I think users have ultimately been pretty fine with how the kubeconfig works and it's been reliable.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

See: #850

[BenTheElder]

/lifecycle active

[aojea]

/close

fixed by #1029

[k8s-ci-robot]

@aojea: Closing this issue.

In response to this:

/close

fixed by #1029

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.