[FLINK-26538] Ability to restart deployment w/o spec change

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: kubernetes-operator-0.1.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: WenJun Min
• Reporter: Thomas Weise
• Created: 08/Mar/22 18:07
• Updated: 27/Mar/22 14:55
• Resolved: 27/Mar/22 14:55

Description

Operator should allow restart of the Flink deployment w/o any other spec change. This provides the escape hatch for an operator to recover a deployment that has gone into a bad state (for whatever reason including memory leaks, hung JVM etc.) without direct access to the k8s cluster. This can be addressed by adding a restartNonce to the CRD.

 

Issue Links

• links to: GitHub Pull Request #85