Enable to switch context when kubeconfig used for login
What would you like to be added
- [x] Add contexts in kubeconfig into user menu. @shu-mutou #4534
- [x] Store kubeconfig in browser side. @shu-mutou #4534
- [x] Re-login when current context is switched. @shu-mutou #4534
- [x] Store
serverforclusterin kubeconfig into cookie. @shu-mutou #4534 - [x] Create client for
serverin each request. @shu-mutou #4534 - [x] Store
sidecarHostforclusterin kubeconfig into cookie. @shu-mutou #4534 - [x] Create client for metrics plugin in each request. @shu-mutou #4534
- [ ] Auto namespace selection when context has namespace attribute.
- [ ] Add edit view for kubeconfig with validation.
Or for only
serverandsidecarHost. Into login view and local setting view. - [ ]
All Clusteroption
Why is this needed
To enable to switch context from browser, rather than switching by kubectl proxy.
Comments

/assign shu-mutou
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.
Nice idea! Added config editor with validation to this spec.
Is it possible we could have an all-clusters option, kinda like all namespaces that shows an aggregated view as well?
@ivelichkovich All Clusters option added into this issue. It will be impremented in the future, but not 2.0.0. Thanks! 😉
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
/lifecycle frozen
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
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
/lifecycle frozen