fix: add api.riotpiao.com to CoreDNS rewrites
Problem: In-cluster pods (portfolio, services) couldn't resolve api.riotpiao.com because it was missing from CoreDNS rewrite rules. This broke LLM API calls from portfolio → api gateway even with valid JWT. Solution: Add rewrite rule to route api.riotpiao.com through nginx ingress (TLS termination + Host header preservation), matching pattern for other internal hostnames (authentik.riotpiao.com, minio.riotpiao.com, etc). Impact: - Portfolio pod now successfully resolves api.riotpiao.com - LLM API calls proceed to auth/permission checking - Applies to all in-cluster services needing LLM gateway
This commit is contained in:
@@ -35,6 +35,7 @@
|
||||
rewrite name longhorn.riotpiao.com ingress-nginx-controller.ingress-nginx.svc.cluster.local
|
||||
rewrite name paperless.riotpiao.com ingress-nginx-controller.ingress-nginx.svc.cluster.local
|
||||
rewrite name img.riotpiao.com ingress-nginx-controller.ingress-nginx.svc.cluster.local
|
||||
rewrite name api.riotpiao.com ingress-nginx-controller.ingress-nginx.svc.cluster.local
|
||||
rewrite name riotpiao.com ingress-nginx-controller.ingress-nginx.svc.cluster.local
|
||||
|
||||
kubernetes cluster.local in-addr.arpa ip6.arpa {
|
||||
|
||||
Reference in New Issue
Block a user