-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add Support for --kubeconfig flag in skaffold run/dev commands #2699
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
Comments
this should be relatively easy to implement, it's a medium sized work, we need to make sure we test for these too:
|
Could I work on this ? |
Hi @marti1125, absolutely! |
@marti1125 Are you still working on this? If you need input or support feel free to ping me. |
yes please I need help @corneliusweig at slack |
I found your message in the #skaffold channel and pinged you. If feasible, I would prefer to keep the conversation on github though. |
ping @marti1125 @corneliusweig are you looking at this? It would be important for us to move forward with it. Let me know! |
@marti1125 Would you be ok if I send a PR and you do a review round on it? Given the priority of the issue this might be a good alternative. WDYT? |
@corneliusweig yes please |
Skaffold run/dev commands support the --kube-context flag to get the context name, but relies on the KUBECONFIG env variable to get the list of kubeconfig file(s).
The ask is below:
Like the kubectl, support --kubeconfig flag that takes a single kubeconfig file path and prefer this flag over the KUBECONFIG env variable when both are present.
Adding this flag will enable us to specify the exact kubeconfig file and the context name that we want to work with, in a consistent way.
Reference: https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig
The text was updated successfully, but these errors were encountered: