fix(kube): correctly resolve client config per context#388
Merged
Conversation
Signed-off-by: Evgeniy Frolov <evgeniy.frolov@flant.com>
There was a problem hiding this comment.
Pull request overview
Fixes kubeconfig context resolution when building Kubernetes clients for all contexts, ensuring each client is created using its own context rather than reusing a single (possibly user-specified) context.
Changes:
- Load the raw kubeconfig without forcing a specific context to enable enumerating all contexts correctly.
- Resolve per-context
clientcmd.ClientConfigusing the iteratedcontextNamewhen constructing each client.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: Evgeniy Frolov <evgeniy.frolov@flant.com>
ilya-lesikov
approved these changes
Feb 12, 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.
No description provided.