SEZ9 commented on issue #11662: URL: https://github.com/apache/seatunnel/issues/11662#issuecomment-5203023317
Thanks for the detailed report and root cause analysis in LogService. Confirmed: /logs builds absolute URLs from member.getAddress().getHost(), which breaks behind Ingress, while /log already uses relative links. This is a valid bug/limitation affecting Kubernetes deployments. Of the two suggested fixes, relative links (option 2) only work when the proxy routes all members under one host, which isn't true for multi-node clusters where /logs aggregates links to different members. A configurable public URL/host per node (option 1, e.g. seatunnel.engine.http.public-url) is likely needed; possibly both together. Would you be willing to submit a PR? As a workaround until this is fixed, you can fetch logs via the current-node /log endpoint (relative links) on each member, or rewrite the member-IP URLs at the ingress/proxy layer if your topology allows it. <!-- streview-comment:55 --> -- 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]
