[
https://issues.apache.org/jira/browse/FLINK-33634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17789478#comment-17789478
]
Tony Garrard commented on FLINK-33634:
--------------------------------------
So we would use the io.fabric8.kubernetes.api.model.Condition class. I think
the first condition type to implement would be _type: Ready_ which we could use
when FlinkApplication/FlinkSessionJob is fully running and FlinkSessionCluster
is ready to accept jobs. Later we could add additional types e.g. _type:
Warning_ to inform the user that for example their FlinkDeployment is using
emphermal storage. Interesting article about conditions here
https://maelvls.dev/kubernetes-conditions/
> 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
>
> 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)
