Bensky/kubeconfig flag #545
Merged
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
Fairwinds Insights Scan ResultsView the full report at insights.fairwinds.com. ✅ No new Action Items detected! |
bbensky
force-pushed
the
bensky/kubeconfig-flag
branch
from
82f8bd3 to
ec80be4
Compare
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.
This PR fixes #540
Checklist
Description
What's the goal of this PR?
Enable
--kubeconfigflag to be passed in withplutocommands.What changes did you make?
Added the
--kubeconfigflag as an option for the commands that require kubectl clients.What alternative solution should we consider, if any?