[jira] [Closed] (FLINK-28494) Add new job status states to CRD

["Gyula Fora (Jira)" <ji...@apache.org>]

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

Gyula Fora closed FLINK-28494.
------------------------------
    Resolution: Won't Fix

> Add new job status states to CRD
> --------------------------------
>
>                 Key: FLINK-28494
>                 URL: https://issues.apache.org/jira/browse/FLINK-28494
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Daren Wong
>            Assignee: Daren Wong
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.2.0
>
>
> The following job info are currently not available in the [jobStatus|https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/crd/status/JobStatus.java] under the Operator [CRD|https://github.com/apache/flink-kubernetes-operator/blob/main/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml]: # endTime – job’s end time, defaults to “-1” for streaming job.
>  # duration – duration of the running job from start to now.
>  # jobPlan – contains job graph info such as parallelism.
> We propose to add the 3 states above into the CRD. Although this stems from an internal requirement for AWS KDA, we foresee that these 3 states could be beneficial to other Flink Kubernetes Operator users/applications as well. These 3 states are readily available via Flink REST client endpoints (I.e “/jobs/:jobid”), which means that the states are exposed for Flink dashboard and other applications. Therefore, we see potential value to others from exposing these 3 job status states in the CRD.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)