[FLINK-15154] Change Flink binding addresses in local mode

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.9.1
• Fix Version/s: 1.11.0
• Component/s: Runtime / Coordination
• Labels: pull-request-available usability

Environment

```
$ uname -a
Linux xxx 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux
```

• Assignee: Xintong Song
• Reporter: Andrea Cardaci
• Created: 09/Dec/19 12:15
• Updated: 13/May/20 08:53
• Resolved: 13/May/20 08:53

Description

Flink (or some of its services) listens on three random TCP ports
during the local[1] execution, e.g., 39951, 41009 and 42849.

[1]: https://ci.apache.org/projects/flink/flink-docs-stable/dev/local_execution.html#local-environment

The sockets listens on `0.0.0.0` and since I need to run some
long-running tests on an Internet-facing machine I was wondering how
to make them listen on `localhost` instead or if there is anything
else I can do to improve the security in this scenario.

Here's what I tried (with little luck):

```
Configuration config = new Configuration();
config.setString("taskmanager.host", "127.0.0.1");
cconfig.setString("rest.bind-address", "127.0.0.1"); // OK
config.setString("jobmanager.rpc.address", "127.0.0.1");
StreamExecutionEnvironment env = StreamExecutionEnvironment.createLocalEnvironment(StreamExecutionEnvironment.getDefaultLocalParallelism(), config);
```

Only the `rest.bind-address` configuration actually changes the
binding address of one of those ports. Are there other parameters that
I'm not aware of or this is not the right approach in local mode?

Issue Links

• is related to: FLINK-13717 allow to set taskmanager.host and taskmanager.bind-host separately
• relates to: FLINK-15911 Flink does not work over NAT
• links to: GitHub Pull Request #12022