Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable to switch context when kubeconfig used for login #4522

Open
7 of 10 tasks
shu-mutou opened this issue Nov 12, 2019 · 10 comments
Open
7 of 10 tasks

Enable to switch context when kubeconfig used for login #4522

shu-mutou opened this issue Nov 12, 2019 · 10 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone

Comments

@shu-mutou
Copy link
Contributor

shu-mutou commented Nov 12, 2019

What would you like to be added
Why is this needed

To enable to switch context from browser, rather than switching by kubectl proxy.

Comments

switch_context

@shu-mutou shu-mutou added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 12, 2019
@shu-mutou
Copy link
Contributor Author

/assign shu-mutou

@floreks
Copy link
Member

floreks commented Nov 12, 2019

That looks really interesting. How about adding an option to local settings on settings view to add new API server config. We could ping it before adding to see if it's up. Then on settings view we could switch contexts and trigger re-login.

Also, it would be good to show available contexts on the login view.

@shu-mutou
Copy link
Contributor Author

Nice idea! Added config editor with validation to this spec.

@ivelichkovich
Copy link
Contributor

Is it possible we could have an all-clusters option, kinda like all namespaces that shows an aggregated view as well?

@shu-mutou
Copy link
Contributor Author

@ivelichkovich All Clusters option added into this issue. It will be impremented in the future, but not 2.0.0. Thanks! 😉

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2020
@shu-mutou shu-mutou removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 20, 2020
@maciaszczykm
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 21, 2020
@shu-mutou shu-mutou removed the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 25, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 22, 2020
@maciaszczykm
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants