You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "David Radley (Jira)" <ji...@apache.org> on 2026/03/18 15:03:00 UTC

[jira] [Resolved] (FLINK-33634) Add Conditions to Flink CRD's Status field

     [ https://issues.apache.org/jira/browse/FLINK-33634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Radley resolved FLINK-33634.
----------------------------------
    Release Note: 
Improvement
[FLINK-33634] - Add Running condition to Flink CRD's Status field for FLIP-493
      Resolution: Fixed

> 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
>            Assignee: David Radley
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.15.0
>
>
> 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)