-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
connect_get_namespaced_service_proxy_with_path messes up response #2158
Comments
Could you elaborate what's the difference between the two responses? |
The webservice that I'm trying to connect will return a JSON list of strings (with doublequotes):
If the return value would be a |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
What happened (please include outputs or screenshots):
Im running
connect_get_namespaced_service_proxy_with_path(name, namespace, path="actuator")
to get JSON data from my webservice.The result is a JSON list:
["foo", "bar"]
but the function returns
['foo', 'bar']
What you expected to happen:
The function to return
["foo", "bar"]
or to return the list or a bytearray.How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
It looks like the deserialisation messes it up. It can be worked around by passing
_preload_content=False
Environment:
kubectl version
): v1.25.13python --version
): Python 3.9.17pip list | grep kubernetes
): 28.1.0The text was updated successfully, but these errors were encountered: