Cluster-from-kubeconfig relies on us generating a kubeconfig; do we want to do that

[justinsb]

Q: How important is the "default cluster from kubeconfig" behaviour to user experience? Should we try to reinstate that behaviour by exporting kubeconfig by default?

Background

Historically, we used the current cluster in kubeconfig to make specifying the cluster name optional for most commands, making the flow a little easier.

Recently we've started not exporting the kubeconfig by default (though you can pass an --admin flag) which means that the cluster name must be specified on every command.

We did this for security, because kubeconfig previously contained non-expiring credentials.

Recently we introduced experimental support for automatically getting a short-lived credential by having kops generate the credential when the current credential had expired. We could therefore safely export a kubeconfig by default again (from a security point of view), except that this functionality is relatively new and not particularly widely tested.

[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

[olemarkus]

@justinsb guess this can be closed now?

Just running kops export kubecfg --admin also works, defaulting to the current context

/remove-lifecycle rotte

[olemarkus]

/remove-lifecycle rotten

[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-contributor-experience at kubernetes/community.
/lifecycle stale

[olemarkus]

I think we have more or less solved this one now

/close
/remove-lifecycle stale

[k8s-ci-robot]

@olemarkus: Closing this issue.

In response to this:

I think we have more or less solved this one now

/close
/remove-lifecycle stale

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.