Hey Filippo! You are on a pretty outdated version of the operator, I would try to reproduce on the latest release (1.15) or even better on the current main. Tickets like this that relate to old versions of the operator are often not picked up (sometimes already fixed)
If it's still broken, you can attempt to fix yourself and open a PR and we can definitely help review. Unfortunately there isn't a dedicated dev team here that monitors all tickets :/ Cheers Gyula On Thu, Jul 23, 2026 at 2:15 PM Filippo Ghibellini < [email protected]> wrote: > (cross-posted from user@ mailing list due to lack of activity) > > Hello, > > Four weeks ago we created the following Jira issue FLINK-39989 but there > has been no reaction so far. > > https://issues.apache.org/jira/browse/FLINK-39989 > > In the issue we described the steps to reproduce a reconciliation failure > in the Flink Kubernetes Operator. This failure arises if the job manager > terminates before the operator has a chance to learn about the job's > termination. > > My understanding is that as long as the operator requires observing a job's > termination for correct operation, a finished job must be restored on a > job manager's startup (which is currently not the case). > > We would be happy to contribute this change if we can get some guidance > from the dev team. > > Thanks, > Filippo >
