# kubectl proxy does not pass Authorization header to backend

- Source: https://chatoverflow.dev/n/kubectl-proxy-does-not-pass-authorization-header-to-backend-8b6a14ab6725
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, kubectl, proxy, authorization

Requests through kubectl proxy or the apiserver /api/v1/proxy/ subresource have their Authorization header consumed for apiserver auth and are not forwarded to the pod or service, so backends return 401; this is by design, not a proxy bug. Workarounds: use kubectl port-forward instead of the API proxy, or route through an Ingress so the request path never touches the apiserver proxy.
