certs should be per-profile

[tstromberg]

SetupCerts is not profile aware, and very racy.

It constantly overwrites the certificates every time you run minikube start, which is bad if two are started at the same time. We should make it so that clusters are updated to use per-profile certs to avoid raciness.

[tstromberg]

This has a WIP PR: #4968

[ghost]

I was running into this issue while trying to let users create their own test clusters at a shared box.

Is there a similar issue for the following files, which need to be separated as well?

/tmp/juju-kubeconfigUpdate
/tmp/juju-kube-config

In addition, is it safe using a shared user for now (e.g. via sudo -u <user> minikube ...) to manage different "profiles"?
As far as I understood from the code (from juju/mutex_flock), these files only get used for locking temporarily, correct?
May I also ask why these temporary files never actually seem to get deleted?

[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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten