Apache Flink

:wave: Hello! I was reading the Flink Kubernetes Operator documentation and noticed that if you want to redeploy a Flink job from a specific snapshot, you must follow these <https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.3/docs/custom-resource/job-management/#manual-recovery|manual recovery steps>. Are there plans to streamline this process? Deploying from a specific snapshot is a relatively common operation and it'd be nice to not need to delete the FlinkDeployment

I wonder if the Flink Operator could use the `initialSavepointPath` similar to the `restartNonce` and `savepointTriggerNonce` parameters, where if `initialSavepointPath`  changes, the deployed job is restored from the specified savepoint. Any thoughts?

And this is probably better suited for the Dev mailing list

Ah sorry about that, sure I'll post it to the dev mailing list :+1: