[ https://issues.apache.org/jira/browse/FLINK-33634 ]
Ryan van Huuksloot deleted comment on FLINK-33634:
--------------------------------------------
was (Author: JIRAUSER285640):
Thoughts on converting the current Status representations to Conditions prior
to adding more Conditions? We can then deprecate the current Statuses. From my
perspective the Statuses that exist today is the Flink Operator's version of
Conditions and it would be good to centralize/standardize them.
Example (Flink Deployment):
status:
conditions:
- type: JobManager
lastTransitionTime: '2023-11-23T12:38:51Z'
> 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)
