8000 Refresh context from kubeconfig · Issue #2824 · derailed/k9s · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Refresh context from kubeconfig #2824

New issue

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

Sign up for GitHub

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

Jump to bottom
Closed
Subbeh opened this issue Aug 8, 2024 · 1 comment
Closed

Refresh context from kubeconfig #2824

Subbeh opened this issue Aug 8, 2024 · 1 comment
Labels
stale

Comments

@Subbeh
Copy link
Subbeh commented Aug 8, 2024 •
edited
Loading




Is your feature request related to a problem? Please describe.
I have processes outside of k9s that change the current context (cluster and namespace) in the kubeconfig. In order to see these changes in k9s, I would either need to manually change this in the active k9s session, or stop and start k9s.

Describe the solution you'd like
Either a keybinding or automated refresh to read the kubeconfig file and change the context accordingly in the UI.

Describe alternatives you've considered
Setting reactive to true in the config file does not seem to work for this situation.

Additional context
N/A
@rotarur
Copy link
rotarur commented Oct 18, 2024

how is this going on? I have the same issue when changing the context outside of k9s it doesn't reflect in live

@github-actions github-actions bot added the stale label May 22, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Subbeh @rotarur
0