fix(gateway): allow egress to ingress-nginx for JWKS #70

Merged
rock merged 1 commits from feat/gateway-egress-jwks into main 2026-10-27 08:37:25 +00:00
Member

NetworkPolicy ipBlock 10.96.0.0/12 misses the real service CIDR 10.106.0.0/16. JWKS fetch hung, callers got 403, pod failed liveness. Allow 443 to the ingress-nginx namespace.

NetworkPolicy ipBlock 10.96.0.0/12 misses the real service CIDR 10.106.0.0/16. JWKS fetch hung, callers got 403, pod failed liveness. Allow 443 to the ingress-nginx namespace.
poimen added 1 commit 2026-10-27 08:37:12 +00:00
fix(gateway): allow egress to ingress-nginx for JWKS
CI / CI (pull_request) Successful in 2m20s
CI / CI (push) Successful in 3m20s
67fe20d7a3
The service CIDR is 10.106.0.0/16, so the ipBlock 10.96.0.0/12 never covered
ingress-nginx (10.101.128.185). The JWKS fetch to zitadel.riotpiao.com therefore
hung until the context deadline: every caller got 403, and the pod failed its
liveness probe before serving traffic.

Add an egress rule for TCP 443 to the ingress-nginx namespace and point jwksUrl
back at the public host. The ZITADEL service port 8080 answers 404 for
/oauth/v2/keys, so the service endpoint is not usable.
rock merged commit 67fe20d7a3 into main 2026-10-27 08:37:25 +00:00
Sign in to join this conversation.