[
https://issues.apache.org/jira/browse/FLINK-29327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605955#comment-17605955
]
Zhenqiu Huang edited comment on FLINK-29327 at 9/16/22 8:56 PM:
----------------------------------------------------------------
It is true that it doesn't impact the functionality. But from user experience,
it is confusing for users to see configures that are not specified by
themselves. Specially, when user can see the cluster level config
kubernetes.operator.plugins.listeners.kafka-dr.private.key.location, it has
also security concern.
was (Author: zhenqiuhuang):
It is true that it doesn't impact the functionality. But from user experience,
it is confusing for users to see configures that are not specified by
themselves. Specially, when user can see the cluster level config
kubernetes.operator.plugins.listeners.kafka-dr.private.key.location, it is also
we security concern.
> Operator configs are showing up among standard Flink configs
> ------------------------------------------------------------
>
> Key: FLINK-29327
> URL: https://issues.apache.org/jira/browse/FLINK-29327
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.1.0
> Reporter: Matyas Orhidi
> Priority: Major
> Fix For: kubernetes-operator-1.2.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
