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
When using kube-rs over kubectl proxy kube-rs client doesn't work while kubectl does
kubectl proxy
kubectl config set-cluster testt --server=http://localhost:8001 --insecure-skip-tls-verify=true kubectl config set-context testt --cluster=testt kubectl config use-context testt
add in ~/.kube/config
~/.kube/config
users: - name: testt user: password: a username: a
and in the testt context:
testt context
- context: cluster: testt user: testt name: testt
then run kubectl get pods (using kube-rs' kubectl example) and it will fail, while official binary works.
kubectl get pods
Found this while trying to work around metalbear-co/mirrord#2803
No response
doesn't matter
kube-client
No, since #1594 is more important to me, but decided to log this issue for common knowledge.
The text was updated successfully, but these errors were encountered:
#1594
Sorry, something went wrong.
presumably duplicate of #1594 ?
looks like it, closing. please reopen if there's something missing
Hey, it's not a duplicate - in this case it would still fail by supplying wrong auth while kubectl works somehow
No branches or pull requests
Current and expected behavior
When using kube-rs over
kubectl proxy
kube-rs client doesn't work while kubectl doesadd in
~/.kube/config
and in the
testt context
:then run
kubectl get pods
(using kube-rs' kubectl example) and it will fail, while official binary works.Found this while trying to work around metalbear-co/mirrord#2803
Possible solution
No response
Additional context
No response
Environment
doesn't matter
Configuration and features
No response
Affected crates
kube-client
Would you like to work on fixing this bug?
No, since #1594 is more important to me, but decided to log this issue for common knowledge.
The text was updated successfully, but these errors were encountered: