You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2024/01/31 10:23: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=17812641#comment-17812641 ] 

Gyula Fora commented on FLINK-31220:
------------------------------------

Seems like this is indeed a backward incompatible change that may be tricky to apply. While it's not a problem for the already running jobs, but users won't be able to submit the same custom resources without modifications (removing the unsupported/not required fields)

> 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)