Add support for setting kubecontext #377
Open
Conversation
This file contains 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
Initially GetKubeClient was working if the context was set externally This change lets one pass the context while running the utility locally
|
@nikhilsbhat do you have the time to complete this? |
|
@yonahd, Oops! I completely missed this amid other tasks. I'll check it out this week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it?
"In the current version, the
GetKubeClientfunction is designed to operate with an externally set context.When using a
kube-configcontaining multiple cluster configurations, the context must be set outside this utility.This PR allows passing the
kube-contextdirectly, similar to how it’s specified when using tools likekubectlorhelm."PR Checklist
GitHub Issue
Closes [XX-XX]
Notes for your reviewers