Documentation
¶
Overview ¶
Command forge serves pkg/secretbroker/secretbrokertest's git forge over TLS, for the Kubernetes end-to-end test (tests/kube, Task 20385).
In the kind cluster it is github.com: the hub reaches it under that name through a hostAliases entry and trusts the test CA that signed its certificate, so a guarded GitHub lease and a git workspace both take their production paths through the git proxy and arrive here. It honours exactly one credential — the PAT the test stored in the hub — and honours it for every repository it serves, so a refusal of the second repository can only have come from the proxy.
It is a test fixture, not a forge: no TLS options, no access log beyond the counts on stderr, and the PAT is read from a file (a mounted Secret) so it appears in neither the Pod spec nor the process table.