Hi all,
I would like to get feedback on adding a statelessRestartNonce to the Flink
Kubernetes Operator.
Today, if a job normally uses upgradeMode: savepoint or last-state,
triggering a fresh restart currently requires:
1. Changing upgradeMode to stateless
2. Bumping restartNonce
3. Changing upgradeMode back afterward
This temporarily mixes an operational action with the job's steady-state
recovery policy. Users sometimes forget the third step, leaving
subsequent upgrades (deploys or scaling events) stateless and creating a
risk of state loss.
Would the community be open to this approach?
```yaml
spec:
job:
statelessRestartNonce: 42
```
Alternatively, we could name it statelessRedeployNonce.
Thanks,
Luca
