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 2026/08/11 14:12:00 UTC

[jira] [Closed] (FLINK-35746) Add logic to override observed config based on settings observed through REST API

     [ https://issues.apache.org/jira/browse/FLINK-35746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora closed FLINK-35746.
------------------------------
    Fix Version/s: kubernetes-operator-1.16.0
       Resolution: Fixed

merged to main fdfcc695daba16e4f4a8c9a6c08b7f470787de00

> Add logic to override observed config based on settings observed through REST API
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-35746
>                 URL: https://issues.apache.org/jira/browse/FLINK-35746
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Nishita Pattanayak
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.16.0
>
>
> In many cases the Flink operator relies on the user configuration to infer running application/cluster settings. While this is mostly fine, many of these configs can be programmatically changed by the user in their app main method that will ultimately take precedence and can lead to inconsistent behaviour from the operators side.
> To alleviate this we need to add logic to override parts of the observed config based on what we see from the cluster. Such as checkpointing enabled / disabled, checkpoint intervals etc.



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