Skip to content
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 specifying a kubeconfig #675

Open
DaruZero opened this issue Aug 21, 2024 · 0 comments
Open

Support specifying a kubeconfig #675

DaruZero opened this issue Aug 21, 2024 · 0 comments

Comments

@DaruZero
Copy link
Contributor

DaruZero commented Aug 21, 2024

Is this a request for help?: No


Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature request

It would be great to be able to specify a kubeconfig file to use instead of relying only on the default ~/.kube/config. I've tried to workaround this by passing the --helm-extra-args "--kubeconfig $KUBECONFIG_FILE" flag, but the problem is that the extra arg does not (rightfully) get passed to the kubectl commands used to check the installation. So in my case, where I don't even have the ~/.kube/config file but just a runtime-generated kubeconfig file, the trick does not work, as the chart would get correctly installed but the check fails regardless
Another side effect of that workaround is that if there actually is a ~/.kube/config with a current context set to a different cluster than the given one, the kubectl check could pass even if the chart didn't install correctly

I would be willing to work on implementing this feature if necessary. I'd say that an optional --kubeconfig flag available for the install command would be beneficial, and should not have bad implications.

Let me know what you think

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant