Re: Could not resolve ResourceManager address in native kubernetes

2021-05-12 Thread Yang Wang
It seems that the TaskManager pod could not resolve the JobManager address "franz-01.default", which is constructed in "k8s-service-name.namespace". I think you need to check whether the coreDNS is running normally in your K8s cluster. You could start a busybox pod on the same node with TaskManager

Re: Could not resolve ResourceManager address in native kubernetes

2021-05-11 Thread Chesnay Schepler
Pulling in Yang Wang who may shed some light on the matter. You could also have a look at http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Native-kubernetes-setup-failed-to-start-job-td39066.html; while the issue was not actually resolved it may give some hints. On 5/10/202

Could not resolve ResourceManager address in native kubernetes

2021-05-10 Thread Valentin Wallyn
Hi, I'm trying to use Flink on native kubernetes ( https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/deployment/resource-providers/native_kubernetes/) but I have an error even with the example from the documentation. The job get submitted but stays in "created" status until it tim