[
https://issues.apache.org/jira/browse/FLINK-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498523#comment-17498523
]
Thomas Weise commented on FLINK-26139:
--------------------------------------
Good to see this, it is a basic requirement for the operator to be able to
reconcile an upgrade when the current job fails.
CANCELLED: since the job lifecycle is managed by the operator, in which
situation (outside upgrade) would we find the job canceled? Cancellation by
user should probably move the deployment into an error/terminated state?
FINISHED: is this really a job state or should that move the deployment into
suspended or terminated?
> Improve JobStatus tracking and handle different job states
> ----------------------------------------------------------
>
> Key: FLINK-26139
> URL: https://issues.apache.org/jira/browse/FLINK-26139
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
> Attachments: image-2022-02-25-21-22-08-636.png
>
>
> Currently we do not handle any job status changes such as cancellations,
> errors or job completions.
> We should introduce some mechanism to react and deal with these changes and
> expose them in the status as they can potentially affect upgrades.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
