prclin opened a new issue, #9287: URL: https://github.com/apache/seatunnel/issues/9287
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened i was run seatunnel on k8s, and access web ui by ingress, job seperated file log was enabled, when i access job log i got this  > a list of log file url but this is only one log file in seatunnel, it was in which master submits the job; so why we return a list of file url in all seatunnel nodes. and the main problem is that url is accessed by ip address, in k8s, these ip does not reachable outside pods. ```json [ { "node": "172.16.231.215:8080", "logLink": "http://172.16.231.215:8080/logs/job-972471770521010177.log";, "logName": "job-972471770521010177.log" }, { "node": "172.16.13.122:8080", "logLink": "http://172.16.13.122:8080/logs/job-972471770521010177.log";, "logName": "job-972471770521010177.log" }, { "node": "172.16.231.195:8080", "logLink": "http://172.16.231.195:8080/logs/job-972471770521010177.log";, "logName": "job-972471770521010177.log" }, { "node": "172.16.13.71:8080", "logLink": "http://172.16.13.71:8080/logs/job-972471770521010177.log";, "logName": "job-972471770521010177.log" } ] ``` so i can`t get log content. ### SeaTunnel Version 2.3.10 ### SeaTunnel Config ```conf log4j2.properties: rootLogger.appenderRef.file.ref = routingAppender ``` ### Running Command ```shell by apiv2 ``` ### Error Exception ```log no ``` ### Zeta or Flink or Spark Version zeta ### Java or Scala Version 1.8 ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
