fix: cannot rewind body after connection loss error

[alexivanoff]

A fix to prevent "net/http: cannot rewind body after connection loss" errors for #65611

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3b8770a477

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Avoid buffering entire request body in catchAll

catchAll is the fallback path for non-special Kubernetes routes, and this new io.ReadAll(req.Body) forces full in-memory buffering before forwarding instead of streaming. For large or streaming request bodies (for example, proxied aggregated API/service endpoints), this can significantly increase latency and memory usage, and allows a single authenticated large upload to consume substantial heap on the proxy. This should be bounded or gated so retries don’t require unbounded buffering for every request body.

Useful? React with 👍 / 👎.

[jakealti]

Thanks for the hotfix. The actual fix landed in #66605 (merged 2026-05-11), which closes #65611. You can close this PR.