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 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?

Thanks!

Reply via email to