WCQS uses miscweb in a non-standard way. Other miscweb consumers point at miscweb directly from the caches, while WCQS routes all requests through itself and forwards static asset requests to miscweb. This is done so that wcqs can add an auth layer, if auth only existed on the backend requests and not the static assets then auth would have to be integrated into the UI and require frontend development work. The current solution allows the UI to be unaware of the auth.

As this is a unique use case it likely wasn't considered as part of the miscweb design in k8s. We will need to review how things work there and come up with a plan moving forward.