[
https://issues.apache.org/jira/browse/FLINK-32529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maximilian Michels updated FLINK-32529:
---------------------------------------
Fix Version/s: kubernetes-operator-1.6.0
> Optional startup probe for JM deployment
> ----------------------------------------
>
> Key: FLINK-32529
> URL: https://issues.apache.org/jira/browse/FLINK-32529
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.6.0
>
>
> There are certain cases where the JM enters a startup crash loop for example
> due to incorrect HA config setup. With the current operator logic these cases
> require manual user intervention as we don't have HA metadata available for
> the last checkpoint and it also seems like the JM actually started already.
> To solve this properly we suggest adding a default JM startup probe that
> queries the rest api (/config) endpoint.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
