[FLINK-32529] Optional startup probe for JM deployment

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: kubernetes-operator-1.6.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Gyula Fora
• Reporter: Gyula Fora
• Created: 04/Jul/23 08:56
• Updated: 26/Mar/24 06:46
• Resolved: 10/Jul/23 19:26

Description

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. 

Issue Links

• links to: GitHub Pull Request #625