[
https://issues.apache.org/jira/browse/FLINK-33634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883807#comment-17883807
]
david radley commented on FLINK-33634:
--------------------------------------
[~gyfora] [~ryanvanhuuksloot] - it would be great if you could review the Flip
document.
For session mode, we are thinking of ready (as in ready to process jobs) - I
know Ryan you were not keen on this. [~lajithk] can we look at using a
different word?
For the application mode with one job running then the condition would be the
Flink job state, having a condition for each state. The only part we are not
sure on is the application mode with multiple jobs - which we are
testing/investigating.
WDYT?
fyi [~mnuttall]
> 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)
