feat(desktop): validate kubeconfig on desktop load #6791
Merged
mlhiter merged 5 commits intolabring:release-v5.1from Mar 13, 2026
Merged
feat(desktop): validate kubeconfig on desktop load #6791mlhiter merged 5 commits intolabring:release-v5.1from
mlhiter merged 5 commits intolabring:release-v5.1from
Conversation
Member
|
tested? @zjy365 |
…ale sessions After kubeconfig rotation, other sessions holding the old kubeconfig are not kicked out. Add a validation check that uses the session's kubeconfig to call k8s API on desktop load. If the old token is revoked (401), the global axios interceptor automatically clears the session and redirects to the signin page. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
mlhiter
approved these changes
Mar 13, 2026
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
2 participants
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.
After kubeconfig rotation, other sessions holding the old kubeconfig are not kicked out. Add a validation check that uses the session's kubeconfig to call k8s API on desktop load. If the old token is revoked (401), the global axios interceptor automatically clears the session and redirects to the signin page.