feat: support alternative kubectl binaries #2639
Open
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.
Proposed solution to #1514
There's not an easy & effective way, that I know of, to check for aliases within Go without running a bash shell in interactive mode and parsing the output. You then have to account for different shells, security risks etc
This seems like a straightforward way to support different
kubectl
binaries. It could alternatively be extracted into a flag.For most users who have the
kubectl
binary as standard, this doesn't introduce any extra system calls