[
https://issues.apache.org/jira/browse/FLINK-40639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18127540#comment-18127540
]
sepuri sai krishna commented on FLINK-40639:
--------------------------------------------
[~panyuepeng] could you assign this one to me, or take it over if you would
rather have it in your own series?
It is a two line fix in KubernetesConfigOptions, one for each of the jobmanager
and taskmanager pod template options, plus a test. PR #29167 was approved by
Jackeyzhe on 20 September, Azure is green and it still merges cleanly. The
release note is on this ticket.
It touches the same withFallbackKeys calls as FLINK-40819, so if you would
rather fold it into that, that works for me too.
> 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)
