[
https://issues.apache.org/jira/browse/FLINK-40639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121212#comment-18121212
]
sepuri sai krishna commented on FLINK-40639:
--------------------------------------------
[~martijnvisser] could you assign this one to me? Jackeyzhe gave it a +1 on the
PR on 20 Sep and CI is green, so it just needs a committer.
https://github.com/apache/flink/pull/29167
The change is one line in each of the two pod template options,
withFallbackKeys -> withDeprecatedKeys, plus a small
KubernetesConfigOptionsTest. The release note is filled in.
> Deprecated kubernetes.pod-template-file takes precedence over
> kubernetes.pod-template-file.default
> --------------------------------------------------------------------------------------------------
>
> Key: FLINK-40639
> URL: https://issues.apache.org/jira/browse/FLINK-40639
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Reporter: sepuri sai krishna
> Priority: Major
> Labels: pull-request-available
>
> With both keys set:
> {noformat}
> kubernetes.pod-template-file: /old.yaml
> kubernetes.pod-template-file.default: /new.yaml
> {noformat}
> the JobManager and TaskManager pod templates resolve to {{/old.yaml}}. The
> deprecated key wins over the current one.
> Expected: the current key should take precedence over the deprecated one.
> Users who move to the new key but leave the old one in their configuration
> keep
> running the old pod template without noticing.
> Reproduced on master. I have a fix and tests ready, could someone assign this
> to
> me?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
