Re: I hit a bad jobmanager address when trying to use Flink SQL Client

Hi Robert! Sorry for the delay. This worked! Thanks! I used slightly different deployment parameters. deployment: gateway-address: flink-jobmanager gateway-port: 8081 On Mon, Sep 14, 2020 at 6:21 AM Robert Metzger wrote: > Hi Dan, > > I don't think the SQL Client officially supports run

Re: I hit a bad jobmanager address when trying to use Flink SQL Client

Hi Dan, I don't think the SQL Client officially supports running against Kubernetes. What you could try is using an undocumented, untested feature: Put something like jobmanager: kubernetes into the "deployment:" section of the Sql Client configuration

Re: I hit a bad jobmanager address when trying to use Flink SQL Client

Hi Dan, Can you verify from the pod that jobmanager and *10.98.253.58:8081 *is actually accessible (e.g., with curl)? I'd probably also try out localhost:8081 as you are connecting to the respective pod directly. On Fri, Sep 11, 2020 at 9:59 PM Dan Hill wrote: > Hi Ro

Re: I hit a bad jobmanager address when trying to use Flink SQL Client

Hi Robert! I have Flink running locally on minikube. I'm running SQL client using exec on the jobmanager. kubectl exec pod/flink-jobmanager-0 -i -t -- /opt/flink/bin/sql-client.sh embedded -e /opt/flink/sql-client-defaults.yaml Here's the sql-client-defaults.yaml. I didn't specify a session. e

Re: I hit a bad jobmanager address when trying to use Flink SQL Client

Hi Dan, the notation of "flink-jobmanager/10.98.253.58:8081" is not a problem. It is how java.net.InetAddress stringifies a resolved address (with both hostname and IP). How did you configure the SQL client to work with a Kubernetes Session? Afaik this is not a documented, tested and officially s

I hit a bad jobmanager address when trying to use Flink SQL Client

I just tried using the Flink SQL Client. A simple job is not running because it cannot hit jobmanager. I'm not sure why Flink SQL Client is hitting "flink-jobmanager/10.98.253.58:8081". I'd expect either "flink-jobmanager:8081" or "10.98.253.58:8081" (which should work with my kubernetes setup).