You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/02/28 11:29:05 UTC

[GitHub] 1u0 opened a new pull request #7858: [FLINK-11127] Update Kubernetes resources: workaround to make TM reachable from JM in Kubernetes

1u0 opened a new pull request #7858: [FLINK-11127] Update Kubernetes resources: workaround to make TM reachable from JM in Kubernetes
URL: https://github.com/apache/flink/pull/7858
 
 
   ## What is the purpose of the change
   
   * This PR adds configuration update (Kubernetes resource definitions) as workaround for [[FLINK-11127]](https://issues.apache.org/jira/browse/FLINK-11127) for Flink `1.7` release branch. With this change, the TMs should be advertising themselves to JM using their k8s pods' ip addresses instead of (by default) hostnames.
   
   **NB:** this patch is supposed only for Flink `1.7` release branch. Flink `1.8` and higher have introduced a new configuration option to mitigate this (`taskmanager.network.bind-policy`).
   
   ## Brief change log
   
     - Example Kubernetes resources are updated to use pods ip address as TMs host address
   
   ## Verifying this change
   
   This change is a trivial rework / code cleanup without any test coverage.
   
     - Manually verified the change by running a cluser with 1 JobManagers and 2 TaskManagers in a minikube.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (**yes** / no / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services