Vaibhav Pathak 1983d12724 fix: use in-cluster Gitea URL for backstage proxy target
The /gitea/api proxy was pointing at the external Gitea hostname which
is unreachable from inside the Kubernetes cluster (no hairpin NAT). Switch
to the in-cluster service DNS, set secure: false for plain HTTP, and
remove the redundant 'Basic ' prefix from the Authorization header.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-21 14:51:05 +05:30
..
2026-02-26 16:58:10 +05:30
2026-03-23 10:28:16 +05:30