We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I had a kubeconfig byte with multiple contexts and current-context in kubeconfig is not what I want to used when build a helm client.
current-context
KubeConfClientOptions.KubeContext
NewClientFromKubeConf
All operation execute by the client should still use the original context in kubeconfig
api.Config
CurrentContext
rest.Config
NewClientFromRestConf
Looks like KubeConfClientOptions.KubeContext do not change the behavior of RESTClientGetter creating any k8s client
RESTClientGetter
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I had a kubeconfig byte with multiple contexts and
current-context
in kubeconfig is not what I want to used when build a helm client.What I expected
KubeConfClientOptions.KubeContext
to what I want to use.NewClientFromKubeConf
.What actually happen
All operation execute by the client should still use the original context in kubeconfig
What I do to workaroud
api.Config
and setCurrentContext
to what I want.api.Config
torest.Config
NewClientFromRestConf
.Looks like
KubeConfClientOptions.KubeContext
do not change the behavior ofRESTClientGetter
creating any k8s clientThe text was updated successfully, but these errors were encountered: