-
Notifications
You must be signed in to change notification settings - Fork 442
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support kubeconfig options when using kubectl command #1057
Conversation
Can one of the admins verify this patch? |
@pixie-io-buildbot test this please |
Thanks for your contribution! |
@JamesMBartlett I've updated the commit message. |
@pixie-io-buildbot test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM just a small nit on using an environment variable instead of a flag
@pixie-io-buildbot test this please |
Can you please GPG sign your commit? See https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits |
Summary: When deploy using `px --kubeconfig THE_KUBE_FILE deploy`, it failed with error `✕ Kubectl > 1.10.0 is present ERR: exit status 1`. And I found the px cli has the `--kubeconfig` option, but the internal kubectl command didn't respect it. Relevant Issues: N/A Type of change: /kind bug Test Plan: Run `px deploy` with `--kubeconfig` option should work without problem. Signed-off-by: Xudong Zhang <felixmelon@gmail.com>
I've signed the commit and rebased. |
@pixie-io-buildbot test this please |
Thanks for your contribution! |
support kubeconfig options when using kubectl command
Summary: When deploy using
px --kubeconfig THE_KUBE_FILE deploy
,it failed with error
✕ Kubectl > 1.10.0 is present ERR: exit status 1
.And I found the px cli has the
--kubeconfig
option, but the internalkubectl command didn't respect it.
Relevant Issues: N/A
Type of change: /kind bug
Test Plan: Run
px deploy
with--kubeconfig
option should work withoutproblem.