[
https://issues.apache.org/jira/browse/FLINK-30405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682544#comment-17682544
]
Zsombor Chikan commented on FLINK-30405:
----------------------------------------
Yeah, you are right maybe I mixed up the 2 things, that is my fault and I
highlighted the less important thing. But that is still true, if I have a
private Resource Lifecycle State field within the CommonStatus class then, that
appears with a different structure within the
`flinkdeployments.flink.apache.org-v1.yml` (and also in the flinksessionjobs)
compared with for example the reconciliation state. My expectation is to have a
commonState property under the 'states' part and within that commonState, there
should be the resourceLifecycleState as a part of the commonState (like in case
of the reconciliationStatus -> reconciliationState). My feeling is that it has
an effect of the final result.
And thank you for the advise, I've already tried that what you mentioned, but
unfortunately '@PrinterColumn' not applicable to methods.
!image-2023-01-31-13-26-23-428.png|width=553,height=79!
I will continue the investigation.
> Add ResourceLifecycleStatus to CommonStatus and printer column
> ---------------------------------------------------------------
>
> Key: FLINK-30405
> URL: https://issues.apache.org/jira/browse/FLINK-30405
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Zsombor Chikan
> Priority: Major
> Labels: starter
> Fix For: kubernetes-operator-1.4.0
>
> Attachments: image-2023-01-31-12-15-18-295.png,
> image-2023-01-31-13-26-23-428.png
>
>
> The CommonStatus api already contains a getter for the ResourceLifecycleState
> of a Flink resource.
> We should remove the JsonIgnore annotation to expose this in the status.
> We should also expose this as a printer column instread of the reconciliation
> status that is used currently.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
