You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened (please include outputs or screenshots):
When calling read_namespace_pod method with an empty string, we accidentally hit the list pods endpoint. This can cause unexpected behavior, such as OOMKills, if the number of pods in the cluster is very large.
What you expected to happen:
If an empty string is given, the client should always throw a 404
How to reproduce it (as minimally and precisely as possible):
set the log level of urllib3 to DEBUG
What happened (please include outputs or screenshots):
When calling
read_namespace_pod
method with an empty string, we accidentally hit the list pods endpoint. This can cause unexpected behavior, such asOOMKill
s, if the number of pods in the cluster is very large.What you expected to happen:
If an empty string is given, the client should always throw a 404
How to reproduce it (as minimally and precisely as possible):
set the log level of urllib3 to DEBUG
then call the
read_namespaced_pod method
with an empty string. The log line looks like:Anything else we need to know?:
Environment:
kubectl version
):python --version
)pip list | grep kubernetes
): 29.0.0The text was updated successfully, but these errors were encountered: