One of the issues we're facing at @GitLab is apiServer being hardcoded in a shared spec.json file used for minikube.

It is possible to set this value automatically using:

tk env set environments/jaeger/dev --server-from-context minikube

However, this will still update the file. So it requires a non-shared (possibly copy-pasted from spec.json.example) spec file, so that users don't keep overriding each other.

Some of the suggestions in #390 may help with this.

But I was wondering if it might make sense for tanka to read kubectl config get-contexts and figure out the apiServer dynamically that way at runtime.