Issue setting up Flink in Kubernetes

[Timothy Victor <vi...@gmail.com>]

Hi -

Has there been any update on the below issue?   I am also facing the same
problem.

http://mail-archives.apache.org/mod_mbox/flink-user/201812.mbox/%3CCAC2R2948LQsYu8Nab5P7YDNHHMUoX5i4jmYiS9g7og6iC-1txA@mail.gmail.com%3E

There is a similar issue (
https://stackoverflow.com/questions/50806228/cant-submit-job-with-flink-1-5-cluster)
where task managers cannot reach the job manager, and the solution appeared
to be to add JOB_MANAGER_RPC_ADDRESS to /etc/hosts.   However, the issue
above is slightly different in that the TMs appear to try to use the
Kubernetes pod name to connect.

Thanks

Tim

Re: Issue setting up Flink in Kubernetes

[Gary Yao <ga...@da-platform.com>]

Hi Tim,

There is an end-to-end test in the Flink repository that starts a job
cluster
in Kubernetes (minikube) [1]. If that does not help you, can you answer the
questions below?

What docker images are you using? Can you share the kubernetes resource
definitions? Can you share the complete logs of the JM and TMs? Did you
follow
the steps outlined in the Flink documentation [2]?

Best,
Gary

[1]
https://github.com/apache/flink/blob/81acd0a490f3ac40cbb2736189796138ac109dd0/flink-end-to-end-tests/test-scripts/test_kubernetes_embedded_job.sh#L46
[2]
https://ci.apache.org/projects/flink/flink-docs-release-1.7/ops/deployment/kubernetes.html


On Tue, Jan 29, 2019 at 5:32 AM Timothy Victor <vi...@gmail.com> wrote:

> Hi -
>
> Has there been any update on the below issue?   I am also facing the same
> problem.
>
>
> http://mail-archives.apache.org/mod_mbox/flink-user/201812.mbox/%3CCAC2R2948LQsYu8Nab5P7YDNHHMUoX5i4jmYiS9g7og6iC-1txA@mail.gmail.com%3E
>
> There is a similar issue (
> https://stackoverflow.com/questions/50806228/cant-submit-job-with-flink-1-5-cluster)
> where task managers cannot reach the job manager, and the solution appeared
> to be to add JOB_MANAGER_RPC_ADDRESS to /etc/hosts.   However, the issue
> above is slightly different in that the TMs appear to try to use the
> Kubernetes pod name to connect.
>
> Thanks
>
> Tim
>