-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[8.0.0] connect_get_namespaced_pod_exec return 403 despite kubectl exec
working in shell
#690
Comments
I am getting this same error |
I met the same error:
File "/usr/local/python/python-3.6.5/lib/python3.6/site-packages/kubernetes/stream/stream.py", line 32, in stream |
Ok I found a work around for this issue. When you create the role to grant this permission I had thought that all I needed was this:
but it turns out you need to add both
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is the traceback for calling
connect_get_namespaced_pod_exec
This is my code:
I have used
kubectl exec backend-worker-celery-685f8fddc9-47sfv echo hello world
and that works perfectly fine with the same kubeconfig.I've tried using this code with an elevated permissioned kubeconfig and that works but I do not want to go that route. Is there some other api call that
connect_get_namespaced_pod_exec
is calling that requires the elevated permissions?The text was updated successfully, but these errors were encountered: