DanielLeens opened a new pull request, #535: URL: https://github.com/apache/seatunnel-website/pull/535
## Summary - define Zeta management interfaces to include every network interface that accepts cluster-control traffic, not only HTTP or job-submission APIs - document the packaged ports: Hazelcast member/client traffic on 5801 for hybrid/master nodes and 5802 for separated workers, REST API v1 on the member port when enabled, and REST API v2/Web UI on the separately configured Jetty port (typically 8080) - make the administrative trust boundary explicit for client-to-member and member-to-member traffic, worker/master messages, packet decoding, and compromised workers - add matching English and Chinese content ## Why The existing security page says that access to a management interface is administrative, but it does not explicitly name the Zeta member protocol or state whether worker-to-master protocol processing is inside that trust boundary. This change closes that ambiguity and explains that a report requiring member-protocol access or control of an admitted member must demonstrate a path from outside the administrative boundary. ## Verification - `git diff --check` - parsed `src/pages/security/languages.json` and verified both new keys exist for English and Chinese - cross-checked ports and role behavior against the current `apache/seatunnel` `dev` configuration and server sources - independent Maintainer Review: PASS The full Docusaurus build was not run locally; the pull-request Build and Deploy workflow is the authoritative full-site validation. -- 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]
