[
https://issues.apache.org/jira/browse/FLINK-26261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500441#comment-17500441
]
Thomas Weise commented on FLINK-26261:
--------------------------------------
The remaining work in this PR is to detect a terminal job manager deployment
failure (such as invalid service account) and reflect it in the deployment
status.
> Reconciliation should try to start job when not already started or move to
> permanent error
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-26261
> URL: https://issues.apache.org/jira/browse/FLINK-26261
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Thomas Weise
> Assignee: Thomas Weise
> Priority: Major
> Labels: pull-request-available
>
> When job submission fails, the operator currently keeps trying to find the
> job status. In the case I'm looking at the cluster wasn't created because the
> image could not be resolved. We either need the logic to re-attempt job
> submission or flag the submission as failed so that JobStatusObserver does
> not attempt to check again. We should also capture the submission error as
> event on the CR.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
