[ https://issues.apache.org/jira/browse/FLINK-33634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885712#comment-17885712 ]
david radley commented on FLINK-33634: -------------------------------------- Hi [~ryanvanhuuksloot] , Talking with [~lajithk] at the end of last week we thought that the simplest way was to introduce one condition with type running, true means business as usual - running job(s) or able to run jobs. This will simplify everything - rather than having to manage multiple conditions and think of appropriate names across session and application mode. We will populate the reason with something representative of the detailed state. > Add Conditions to Flink CRD's Status field > ------------------------------------------ > > Key: FLINK-33634 > URL: https://issues.apache.org/jira/browse/FLINK-33634 > Project: Flink > Issue Type: Improvement > Components: Kubernetes Operator > Affects Versions: kubernetes-operator-1.7.0 > Reporter: Tony Garrard > Priority: Major > Labels: pull-request-available > > From > [https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties] > it is considered best practice to provide Conditions in the Status of CRD's. > Some tooling even expects there to be a Conditions field in the status of a > CR. This issue to to propose adding a Conditions field to the CR status > e.g. > status: > conditions: > - lastTransitionTime: '2023-11-23T12:38:51Z' > status: 'True' > type: Ready -- This message was sent by Atlassian Jira (v8.20.10#820010)