Is there any way using Flink Kubernetes Operator t...
# troubleshooting
a
Is there any way using Flink Kubernetes Operator that once a job is marked FINISHED, it automatically scales down the JobManagers? I'm running batches on it and don't need the JMs to stick around.
馃憖 1
s
This seems like a useful feature and +1 this if it doesn't exist. I wonder if it is due to its nature of being kinda like a PaaS so the JobManager is typically used like a self-service type thing to run multiple jobs. The idea that you can create a job from the jobmanager UI or REST api.
Thinking it'd be in here somewhere? https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/configuration/#autoscaler-configuration
kubernetes.operator.jm-deployment.shutdown-ttl : Time after which jobmanager pods of terminal application deployments are shut down.
I don't see anything tho that reads "Time after which jobmanager pods of finished task are shut down" 馃し
a
Paging @Gyula F贸ra - is this possible? If not, is it an interesting feature request? I don't want to use a session cluster really, but if each batch job submission I do via FlinkDeployment gives me JobManagers I have to remove manually, I'm kind of forced to.
g
a
Oh wow, so that does work for job lifecycle = FINISHED?? That's so cool.
g
You can try and see what happens 馃檪 if it doesn鈥檛 work you can open a jira ticket / work on a fix? 馃槃
but chances are good
a
ooo i'll try it and if it doesn't work i'll try and contribute it. thanks