apiserver proxy rewrites v1beta1 URLs to include a namespace in the path #5339
Closed
Description
Today I launched a pod that was serving an angular app without a service or host port. To access the app, I used the proxy in the apiserver (/api/v1beta1/proxy/pods/<pod-id>
). This returned the html of the app but none of the css or javascript loaded. Looking at the console, it appeared that the browser was attempting to load the resources from /api/v1beta1/ns/default/proxy/pods/<pod-id>
(note the addition of the default namespace in the path).
Loading the resources directly (without the namespace) worked as expected. Hitting the URL including the (incorrect) namespace returned a 404.
We should make sure that any URL rewriting we do is versioned appropriately.
/cc @timothysc