[FLINK-26135] Separate job and deployment errors in FlinkDeployment status

• 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: Gyula Fora
• Reporter: Gyula Fora
• Created: 14/Feb/22 16:27
• Updated: 27/Mar/22 13:16
• Resolved: 17/Feb/22 14:52

Description

At the moment the controller does not validate or tolerate any deployment errors such as incorrect configurations etc. Those will lead to an exception loop in the reconcile logic.

There are cases where the job deployment cannot be executed due to incorrect configuration or other causes. In these cases the job can still be running correctly so the job status should be OK but we should signal a deployment error to the user that requires action.

There should be a shared validation logic between the controller and the webhook that should be applied whenever a new FlinkDeployment update is received by the controller. If an error is detected in the controller, set the deployment status to error with a useful message and leave the current job running.

Issue Links

• links to: GitHub Pull Request #5