Hi, We are using Apache Flink Kubernetes operator to manage the deployment lifecycle of our Flink jobs. And we are using the application mode with "last-state" upgrade mode for each FlinkDeployment.
As I know, each FlinkDeployment will keep using the same job id across different job deployments / upgrades, because the operator uses the job failover mechanism to achieve "last-state" upgrade mode. However, with it, it seems impossible to integrate with Flink history server which uses job.id to differentiate different job deployments. Questions: - Is there any way to make the job.id different for "last-state" upgrade mode? - What could be the right way to enable Flink history server in this case?
