757: unexpected token at '404: Page Not Found' happens when having a 404 error about kubeclient HOT 4 CLOSED

This is caused by kubernetes/kubernetes#5491

from kubeclient.

cc @Fryguy

from kubeclient.

I think it's ok to blow up with a JSON parse error on 404. Alternately, you could catch that error in the handling_kube_exception method, and then translate it to a RestClient::ResourceNotFound error if you see "404: Page Not Found" in the page text (or maybe RestClient has a .http_code == 404 which you could check)

from kubeclient.

I think it's ok to blow up with a JSON parse error on 404. Alternately, you could catch that error in the handling_kube_exception method, and then translate it to a RestClient::ResourceNotFound error if you see "404: Page Not Found" in the page text (or maybe RestClient has a .http_code == 404 which you could check)

the problem is that Json.parse fails, and it's hard to predict on which exception it will fail since it wasn't jsonized. For now I am aware of 404 and 500 but there might be more that we'll have to keep track of, to differentiate them from a real non valid json response that might be returned.

from kubeclient.