[
https://issues.apache.org/jira/browse/FLINK-32109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17723130#comment-17723130
]
Gyula Fora commented on FLINK-32109:
------------------------------------
cc [~mbalassi] [~thw]
> Operator doesn't recognize JobManager stuck on volumeMount startup errors
> -------------------------------------------------------------------------
>
> Key: FLINK-32109
> URL: https://issues.apache.org/jira/browse/FLINK-32109
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.5.0, kubernetes-operator-1.6.0
> Reporter: Gyula Fora
> Priority: Major
>
> Currently the flink deployment observer logic only reacts to Deployment
> conditions such as failure to create the JM pod, image pull errors etc.
> Pod startup errors such as volumeMount are not recognized as errors and the
> operator keeps waiting for it indefintitely.
> This is a tricky problem because volumeMount errors can be transient and are
> only reported as Events for the pod so I am not completely sure if we can do
> anything about this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
