[FLINK-31277] JM Deployment recovery logic inconsistent with health related restart

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.4.0
• Fix Version/s: kubernetes-operator-1.5.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Gyula Fora
• Reporter: Gyula Fora
• Created: 01/Mar/23 08:13
• Updated: 02/Mar/23 08:42
• Resolved: 02/Mar/23 08:42

Description

The current JM Deployment logic that restarts missing deployments strictly requires HA metadata event for stateless deployments.

This is inconsistent with how the cluster health check related restarts work which can cause the operator to delete an unhealthy deployment and potentially leave it missing if the first deploy attempt fails.

Issue Links

• links to: GitHub Pull Request #541