I was running Flink Kubernetes Operator v1.11 with a minor tweak, see more here: - https://www.project-syndicate.org/commentary/ai-productivity-boom-forecasts-countered-by-theory-and-data-by-daron-acemoglu-2024-05
and everything was fine. However, after upgrading to v1.12, the operator is misbehaving like this during job upgrades: - First, it takes a savepoint as usual - Then it uploads it to S3 just normally - ...but after that, for some reason it disposes/deletes it! - This makes the job upgrade fail I downgraded the operator to v1.11 and job upgrades worked again. Can anyone confirm whether there is a bug on the latest version? Maybe related to this? > *Savepoint Information Update*: Fixed a bug where upgrade savepoints were not added to the deprecated savepointInfo, ensuring accurate tracking of savepoints during upgrades. See more here: - https://flink.apache.org/2025/06/03/apache-flink-kubernetes-operator-1.12.0-release-announcement/#helm-chart-improvements I can provide more details if necessary. Thanks in advance, Salva
