Skip to content

Authentication issue for new list third party resource endpoint #227

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

Closed
pvdvreede opened this issue May 22, 2017 · 1 comment · Fixed by #230
Closed

Authentication issue for new list third party resource endpoint #227

pvdvreede opened this issue May 22, 2017 · 1 comment · Fixed by #230

Comments

@pvdvreede
Copy link

pvdvreede commented May 22, 2017

Hi @mbohlool I am trying the new tpr resources endpoints and it seems to work fine if I am outside a cluster, but when I run it in a cluster it appears that my call to list_third_party_resource is getting a 401 as there is no auth passed with the request. This is in contrast to the replace_third_party_resource call which seems to work fine.

I did notice that here: https://github.com/kubernetes-incubator/client-python/blob/master/kubernetes/client/apis/third_party_resources_api.py#L487, there is no 'Bearer' in the auth settings like there appears to be in the replace call I do elsewhere.

Is there some configuration on the client generation that is missing?

Thanks.

@mbohlool
Copy link
Contributor

It is a bug in the original tpr spec. I've fixed it in #230. Please review it.

yliaog pushed a commit to yliaog/client-python that referenced this issue Jan 8, 2022
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

Successfully merging a pull request may close this issue.

2 participants