We are using flink operator, when we deploy flinkd...
# troubleshootingk
kingsathurthi
01/17/2023, 5:54 AMWe are using flink operator, when we deploy flinkdeployment, Job Manager, taskmanager and service(UI port:8081) for job manager is automatically created.
My question is how to modify the default port and how to add additional ports in the job manager service?
m
Matyas Orhidi
01/17/2023, 5:56 AMYou can add
rest.portflinkConfigurationMatyas Orhidi
01/17/2023, 5:57 AMYou can use the podTemplate to open up additional ports on the JM/TM pods
k
kingsathurthi
01/17/2023, 5:59 AMRight now I'm manually creating the service for TM.
Does TM service also automatically gets created like JM?
m
Matyas Orhidi
01/17/2023, 6:00 AMNo TMs don't directory exposed as a service.
👍 1
k
kingsathurthi
01/17/2023, 6:01 AMOkay, then thanks
kingsathurthi
01/17/2023, 7:35 AMI have added the additional ports in JM pod template but it doesn't showup in the jm-rest kubenetes service (only rest port 8081 is showing) what i'm missing here
z
Zsombor Chikán
01/17/2023, 7:47 AM@kingsathurthi I am just thinking outloud, but maybe you can create a ConfigMap containing the ports you want to use and mount it as a volume in the Job Manager pod... then, you can set the ports using environment variables in the Job Manager container... maybe in this way, you can easily change the ports without having to rebuild the images
Zsombor Chikán
01/17/2023, 7:52 AMand related to your last note: maybe you also need to update the associated Kubernetes Service resource to make those ports accessible.. and maybe you already done this, but after updating the Service resource, you need to apply the changes to the cluster.. the last only thing is that make sure the additional ports are free, and the JobManager is configured to listen on those ports
k
kingsathurthi
01/17/2023, 8:21 AMThere is no yaml for that associated JM kubernetes service available, it is creating under the hood
m
Matyas Orhidi
01/17/2023, 6:24 PM@kingsathurthi the podTemplate only controls the pods for JM/TM. Not sure what you're trying to achieve here, but this is not a common request for flink applications to expose extra ports as service. Help me understand what you're trying to achieve and we may find a solution for that.
k
kingsathurthi
01/18/2023, 5:05 AMI want to expose the metrics of JM and TM using this port 9250. For TM I'm manually creating the Kubernetes service and exposing metrics port(9250) and other port so its working . But for JM I'm unable to expose the 9250 port because by defalut kubernetes service for JM is automatically getting created
kingsathurthi
01/19/2023, 4:43 AMHi @Matyas Orhidi I tried adding additional port (metric port for prometheus) in JM/TM pod and container port port is working but JM kubernetes service only exposing the
rest.port: 8081