xintongsong opened a new pull request #11284: [FLINK-15911][runtime] Make Flink work with NAT. URL: https://github.com/apache/flink/pull/11284 ## What is the purpose of the change This PR makes Flink work with NAT by introducing separated configuration options for address/port and bind-address/bind-port of JM/TM RPC services and Netty Shuffle Service. ## Brief change log - 592a79c26d047920e5d7ba20ba99c01c926797ec: Minor code clean-ups. - c7f8860864951b33aef27404b1666f0648a26f8b: Refactor to create `AkkaRpsService` with builder class. Currently there are too many nested methods for creating a `AkkaRpsService`, making it hard to understand which changes affect which code paths. - 24fb21896bc3bc95532c925057cca5031a1721a3: Separate config options for JM/TM hostname/bind-hostname and RPC port/bind-port. - 00808b0c3814cf7bd028b069e5b7022e92569c18: Separate config options for Netty Shuffle Service data port/bind-port. - 26db673d7bf7505bd46186fe2c69ffb11c4f76f9: Introduce e2e test for Flink over NAT. - 4683aaeae4a1ee29a403bf6495f2065c539b224f: **DO_NOT_MERGE_THIS** Add the NAT e2e test to pre-commit tests, for the convenience of review. ## Verifying this change Added a docker-based e2e test for verifying Flink works over NAT. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (yes) - If yes, how is the feature documented? (not documented)
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
