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

Posted to issues@flink.apache.org by "Xin Li (Jira)" <ji...@apache.org> on 2023/03/29 02:12:00 UTC

[jira] [Commented] (FLINK-31220) Replace Pod with PodTemplateSpec for the pod template properties

    [ https://issues.apache.org/jira/browse/FLINK-31220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706180#comment-17706180 ] 

Xin Li commented on FLINK-31220:
--------------------------------

Hi [~gyfora], this heard like importing the pod spec in the controller code and needs to keep all optional fields for a while (at least serval versions before announcing the shift). What's the opinion on when to remove some fields like status mentioned?

> Replace Pod with PodTemplateSpec for the pod template properties
> ----------------------------------------------------------------
>
>                 Key: FLINK-31220
>                 URL: https://issues.apache.org/jira/browse/FLINK-31220
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>
> The current podtemplate fields in the CR use the Pod object for schema. This doesn't make sense as status and other fields should never be specified and they take no effect.
> We should replace this with PodTemplateSpec and make sure that this is not a breaking change even if users incorrectly specified status before.



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