[
https://issues.apache.org/jira/browse/FLINK-40639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sepuri sai krishna updated FLINK-40639:
---------------------------------------
Release Note: {{kubernetes.pod-template-file.default}} now takes precedence
over the deprecated {{kubernetes.pod-template-file}}. Deployments that set both
keys previously used the deprecated one and will now use
{{kubernetes.pod-template-file.default}}. Using the deprecated key now also
logs a deprecation warning.
> 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)
