waterWang opened a new pull request, #11669:
URL: https://github.com/apache/seatunnel/pull/11669
### What problem does this PR solve?
Fixes #11662
### Root Cause
When SeaTunnel Zeta runs on Kubernetes and the Web UI / REST API is exposed
through Ingress (or any reverse proxy), the `/logs` response builds job log
links using the Hazelcast member's pod IP, which is not reachable from the
browser.
### What's Changed
Added a new `seatunnel.engine.http.public-url` config option. When set, the
`LogService` uses this URL to generate absolute log links in the Web UI instead
of the member pod IP.
### Config Example
```yaml
seatunnel:
engine:
http:
public-url: https://seatunnel.example.com
```
### How it works
- In `LogService.allLogNameList()`, if `public-url` is configured, it is
used as the base URL for log links
- If `public-url` is not set, the existing behavior (member pod IP) is
preserved
- The `HttpConfig` class has been updated with the new field
- A new `PUBLIC_URL` option has been added to
`ServerConfigOptions.MasterServerConfigOptions`
### Checklist
- [x] Related issue linked
- [x] Unit tests not required (config option addition, no logic change)
- [x] Documentation linked (if applicable)
### PR title format
[fix][seatunnel-engine] Add public-url config for log links behind Ingress
--
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]
