Kubernetes operator and jobs with last-state upgrades

[Alexis Sarda-Espinosa <sa...@gmail.com>]

Hello,

I am doing some tests with the operator and, if I'm not mistaken, using
last-state upgrade means that, when something is changed in the CR, no
savepoint is taken and the pods are simply terminated. Is that a
requirement from Flink HA? I would have thought last-state would still use
savepoints for upgrade if the current status is stable.

Regards,
Alexis.

Re: Kubernetes operator and jobs with last-state upgrades

[zh...@outlook.com]

Hi,

When you use last state upgrade, you simply delete the Flink deployment but keeping HA metadata where checkpoint info is stored, and the upgraded job would recover the state from the latest checkpoint.

Best,
Zhanghao Chen
________________________________
From: Alexis Sarda-Espinosa <sa...@gmail.com>
Sent: Thursday, November 17, 2022 1:24
To: user <us...@flink.apache.org>
Subject: Kubernetes operator and jobs with last-state upgrades

Hello,

I am doing some tests with the operator and, if I'm not mistaken, using last-state upgrade means that, when something is changed in the CR, no savepoint is taken and the pods are simply terminated. Is that a requirement from Flink HA? I would have thought last-state would still use savepoints for upgrade if the current status is stable.

Regards,
Alexis.