You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/04/05 17:22:00 UTC

[jira] [Commented] (FLINK-27023) Merge default flink and operator configuration settings for the operator

    [ https://issues.apache.org/jira/browse/FLINK-27023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517581#comment-17517581 ] 

Nicholas Jiang commented on FLINK-27023:
----------------------------------------

[~gyfora], do anyone work on this ticket? If no, I would like to follow above changes mentioned to merge the configuration.

> Merge default flink and operator configuration settings for the operator
> ------------------------------------------------------------------------
>
>                 Key: FLINK-27023
>                 URL: https://issues.apache.org/jira/browse/FLINK-27023
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Priority: Major
>             Fix For: kubernetes-operator-1.0.0
>
>
> Based on the mailing list discussion : [https://lists.apache.org/thread/pnf2gk9dgqv3qrtszqbfcdxf32t2gr3x]
> As a first step we can combine the operators default flink and operator config.
> This includes the following changes:
>  # Get rid of the DefaultConfig class and replace with a single Configuration object containing the settings for both.
>  # Rename OperatorConfigOptions -> KubernetesOperatorConfigOptions
>  # Prefix all options with `kubernetes` to get kubernetes.operator.....
>  # In the helm chart combine the operatorConfiguration and flinkDefaultConfiguration into a common defaultConfigurationSection. We should still keep the logging settings separately for the two somehow



--
This message was sent by Atlassian Jira
(v8.20.1#820001)