Hi all! I recently came across the FlinkStateSnapshot feature which I found quite interesting, but I had a couple questions on its use.
1. In favor of FlinkStateSnapshots, I see that both the checkpointInfo and savepointInfo have been deprecated as part of the JobStatus of FlinkDeployment. Does this mean these fields will eventually be completely removed? Additionally, would the community consider adding a path field to the existing checkpointInfo? Currently it only shows the triggerId, which isn't as helpful when trying to find the actual checkpoint path. 2. For FlinkStateSnapshots, was is the major benefit of separating out the checkpoint and savepoint info outside of the FlinkDeployment status? I can see the benefit of having some separation, but I feel like I may be missing additional context. 3. Do FlinkStateSnapshots trigger checkpoints by default if periodic checkpointing is enabled? I was using Flink v1_17 and recently tried setting the kubernetes.operator.periodic.checkpoint.interval and although Flink Operator does trigger periodic checkpoints, I did not see the FlinkStateSnapshot status reconcile. I had assumed this status would be populated automatically if the snapshot was configured like in the documentation: https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/custom-resource/snapshots/#checkpoint. Appreciate the help! - Michal
