Hello! The Flink operator currently does not delete the jobmanager pod when a deployment is suspended. This way the rest api stay available but no other resources are consumed (taskmanagers are deleted)
When you delete the FlinkDeployment resource completely, then the jobmanager deployment is also deleted. In theory we could improve the logic to eventually delete the jobmanager for suspended resources but we currently use this is a way to guarantee more resiliency for the operator flow. Cheers, Gyula On Wed, Oct 12, 2022 at 3:56 PM Meghajit Mazumdar < meghajit.mazum...@gojek.com> wrote: > Hello, > > I recently deployed a Flink Operator in Kubernetes and wrote a simple > FlinkDeployment CRD to run it in application mode following this > <https://github.com/apache/flink-kubernetes-operator/blob/main/examples/pod-template.yaml> > . > > I noticed that, even after I edited the CRD and marked the spec.job.state > field as *suspended, *the metric *jobmanager_job_uptime_value *continued > to show the job status as *running*. I did verify that after re-applying > these changes, the JM and TM pods were deleted and the cluster was not > running anymore. > > Am I doing something incorrect or is there some other metric to monitor > the job status when using Flink Operator ? > > > > -- > *Regards,* > *Meghajit* >
