DanielLeens commented on issue #11662: URL: https://github.com/apache/seatunnel/issues/11662#issuecomment-5191585862
Thanks for the detailed reproduction. I checked the current `dev` branch and the report matches the server path today: the log service still builds per-node log URLs from the member host/port and returns those absolute links to the UI, so in an ingress or Kubernetes deployment those links can point to an internal pod/member address instead of the externally reachable host. That makes this a valid bug. The safest first fix is to keep the scope narrow: make the `/logs` and job-log links ingress-safe without changing unrelated monitoring URLs in the same PR, and add a regression test around the externally exposed log-link behavior. If you would like to take it, a focused PR on that boundary would be a good next step. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
