<p>I want to create a new k8s deployment with a session job; and have one <code>taskmanager</code> deployed with a configuration like this in <code>flink-conf.yaml</code>:</p>

<pre><code>jobmanager.rpc.address: analytics-job
jobmanager.rpc.port: 6123
</code></pre>

<p>However, it would seem that my TaskManager refuses to use the port 6123 and always picks a high ports? The analytics job's k8s service looks like this:</p>

<pre><code>apiVersion: v1
kind: Service
metadata:
  name: analytics-job
spec:
  type: ClusterIP
  ports:
  - name: rpc
    port: 6123
  - name: blob
    port: 6124
  - name: query
    port: 6125
    # nodePort: 30025
  - name: ui
    port: 8081
    # nodePort: 30081
  selector:
    app: analytics
    stack: flink
    component: job-cluster
</code></pre>

<p>and as you can see I've tried both ClusterIP and NodePort service types. I'd rather have a ClusterIP type since that creates an internal load balancer in front of my k8s Job/<code>standalone-job.sh</code> Flink process.</p>

Henrik
<p>In flink-conf.yaml, set</p>

<pre><code>high-availability.jobmanager.port: 6123
</code></pre>

<p>That will bring the resource manager connection back down to the static port you'd like it to be using.</p>
