ingress-nginx-egress CNP enumerates the namespaces ingress-nginx may reach; coder wasn't on the list, so requests to coder.renner.uno timed out at the proxy even after coder-ns.yaml allowed the inbound side.
Test plan
curl https://coder.renner.uno/api/v2/buildinfo from an in-cluster pod returns 200
## Summary
- `ingress-nginx-egress` CNP enumerates the namespaces ingress-nginx may reach; `coder` wasn't on the list, so requests to `coder.renner.uno` timed out at the proxy even after `coder-ns.yaml` allowed the inbound side.
## Test plan
- [ ] `curl https://coder.renner.uno/api/v2/buildinfo` from an in-cluster pod returns 200
The per-ingress-nginx egress CNP enumerates app namespaces; coder was
missing, so requests to coder.renner.uno dead-ended at
"upstream timed out" even though coder's own CNP allowed the inbound
side. Add coder to the allowlist, matching the other apps.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
ingress-nginx-egressCNP enumerates the namespaces ingress-nginx may reach;coderwasn't on the list, so requests tocoder.renner.unotimed out at the proxy even aftercoder-ns.yamlallowed the inbound side.Test plan
curl https://coder.renner.uno/api/v2/buildinfofrom an in-cluster pod returns 200