fix: set kubectl context in local terminal to match active cluster#374
Merged
nadaverell merged 2 commits intomainfrom Mar 28, 2026
Merged
fix: set kubectl context in local terminal to match active cluster#374nadaverell merged 2 commits intomainfrom
nadaverell merged 2 commits intomainfrom
Conversation
…uster When opening a local terminal, the shell now gets a temporary kubeconfig with current-context set to the cluster Radar is viewing, so kubectl commands target the right cluster without manual context switching. Fixes #373
nadaverell
force-pushed
the
fix/local-terminal-context
branch
from
930afb8 to
8a8daf5
Compare
Lockfile was missing @tanstack/react-query@5.95.2, tailwindcss@4.2.2, and @tanstack/query-core@5.95.2, causing CI frontend job to fail.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
When opening a local terminal in Radar, the kubectl context wasn't set to the cluster being viewed — it used whatever context was default in the user's kubeconfig. This made running kubectl commands confusing since you had to manually switch context each time.
The fix creates a temporary copy of the kubeconfig with
current-contextset to Radar's active cluster, and points the shell'sKUBECONFIGenv var at it. The temp file is cleaned up when the session ends. Falls back to the original behavior if temp file creation fails.internal/k8s/client.go— newWriteKubeconfigForCurrentContext()helperinternal/server/localterm.go— uses temp kubeconfig + cleanup on session endFixes #373