Re: [PR] [FLINK-33634] Add Conditions to Flink CRD's Status field [flink-kubernetes-operator]

["lajith2006 (via GitHub)" <gi...@apache.org>]

lajith2006 commented on PR #957:
URL: https://github.com/apache/flink-kubernetes-operator/pull/957#issuecomment-2768463731

   As mentioned in the FLIP , we will have status.conditions, which holds the list of conditions that contains the status of Job transitions in each stage. 
   
   When the `FlinkOperator` is installed in Openshift and manages `FlinkDeployment` , with status.conditions in the CR , `FlinkDeployment` status in the Openshift UI will provide some misleading information. 
   
   Openshift UI works in such  a way that, if there are multiple conditions , and at any point one of the condition had a flag of status with true and type as Running , irrespective of latest condition status has a flag as of false and type Running , In Openshift UI , status says that condition of deployment/job is Running. Which is misleading information, if you consider the scenario of Job was running and then later point job was suspended. 
   
   For example as below when a running Job is stopped at some point , we will have a condition as below. 
   
     ```
   conditions:
       - lastTransitionTime: '2025-04-01T06:17:08Z'
         message: Reconciling
         reason: Job is currently reconciling
         status: 'False'
         type: Running
       - lastTransitionTime: '2025-04-01T07:07:23Z'
         message: JobRunning
         reason: Job is running
         status: 'True'
         type: Running
       - lastTransitionTime: '2025-04-01T07:28:37Z'
         message: JobFinished
         reason: Job's tasks have successfully finished
         status: 'False'
         type: Running
   ```
   
   and Openshift UI will have status as 
   
   <img width="1195" alt="Screenshot 2025-04-01 at 1 07 43 PM" src="https://github.com/user-attachments/assets/5e74aa48-3859-488b-9277-96d3a871e101" />
   
   
   
   So to overcome those  problems, we will have a `status.phase`(same as other k8s resources like pod) , which will hold the current status of deployment/job. Openshift UI will take precedence of `status.phase` over `status.condition `to display the status of `FlinkDeployment` resource. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org