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 2022/07/08 12:16:00 UTC

[jira] [Closed] (FLINK-28445) Support operator configuration from multiple configmaps

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

Gyula Fora closed FLINK-28445.
------------------------------
    Resolution: Fixed

Merged to main 56381ecf4515ff12d72fe6b1a245160580aacb72

> Support operator configuration from multiple configmaps
> -------------------------------------------------------
>
>                 Key: FLINK-28445
>                 URL: https://issues.apache.org/jira/browse/FLINK-28445
>             Project: Flink
>          Issue Type: New Feature
>            Reporter: Matyas Orhidi
>            Assignee: Matyas Orhidi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.1.0
>
>
> It is beneficial in certain scenarios to load operator configurations from multiple ConfigMaps. For example the `kubernetes.operator.watched.namespaces` is a typical property maintained by control planes and the rest is by the Operator. By allowing loading the configuration from multiple ConfigMaps the default configuration can be owned by the Operator and other environment specific overrides by a control plane. This also allows upgrading the Operator independently from control planes.



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