[ 
https://issues.apache.org/jira/browse/FLINK-32033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004792#comment-18004792
 ] 

Nishita Pattanayak commented on FLINK-32033:
--------------------------------------------

[~gyfora] Here is a 
[PR|https://github.com/apache/flink-kubernetes-operator/pull/997] for fixing 
these issues. Kindly, do have a look at it. I have covered certain scenarios 
where the `FlinkDeployment` should definitely show FAILED.

> Resource lifecycle state shows stable even if application deployment goes 
> missing
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-32033
>                 URL: https://issues.apache.org/jira/browse/FLINK-32033
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.4.0
>            Reporter: Gyula Fora
>            Assignee: Nishita Pattanayak
>            Priority: Major
>              Labels: pull-request-available
>
> Currently the lifecycle state shows STABLE even if an application deployment 
> was deleted and stays in MISSING / reconciling state. 
> We should consider these FAILED as they won't be recovered.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to