[
https://issues.apache.org/jira/browse/FLINK-26473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501194#comment-17501194
]
Yang Wang commented on FLINK-26473:
-----------------------------------
In the current implementation of {{{}Observer{}}}, when the
{{JobManagerDeploymentStatus}} comes to {{{}READY{}}}, all the subsequent
changes will be ignored(e.g. JobManager k8s deployment may crash backoff,
deleted accidentally). What I means is to make the {{Observer}} could handle
such changes correctly.
> Observer should support JobManager deployment crashed or deleted externally
> ---------------------------------------------------------------------------
>
> Key: FLINK-26473
> URL: https://issues.apache.org/jira/browse/FLINK-26473
> Project: Flink
> Issue Type: Sub-task
> Components: Kubernetes Operator
> Reporter: Yang Wang
> Priority: Major
>
> Follow the discussion in this PR
> [https://github.com/apache/flink-kubernetes-operator/pull/26#discussion_r817514763.]
>
> Currently, the {{observeJmDeployment}} still could not cover some scenarios,
> e.g. JobManager deployment crashed, JobManager deployment was deleted
> externally. When it {{JobManagerDeploymentStatus}} comes to {{{}READY{}}}, it
> will always be {{{}READY{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
