[
https://issues.apache.org/jira/browse/FLINK-30363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645924#comment-17645924
]
Zhenqiu Huang commented on FLINK-30363:
---------------------------------------
Discussed with [~gyfora] offline, the change will wait for the flink upstream
feature.
https://issues.apache.org/jira/browse/FLINK-28831
> Disable HadoppConf and Kerboros Decorator by default
> ----------------------------------------------------
>
> Key: FLINK-30363
> URL: https://issues.apache.org/jira/browse/FLINK-30363
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.1.0
> Reporter: Zhenqiu Huang
> Priority: Minor
>
> Flink natively replies on these two decorator to create config maps and k8s
> secrets before creating job manager pod in K8s. It works well in job
> submisstion through Flink Cli.
> org.apache.flink.kubernetes.kubeclient.decorators.HadoopConfMountDecorator
> org.apache.flink.kubernetes.kubeclient.decorators.KerberosMountDecorator
> But It doesn't work in operator mode:
> 1) Operator class path doesn't had HADOOP or Kerberos related info, so
> resources willn't be created.
> 2) When FlinkResourceManager create TM Pod. If JM POD has HADOOP env
> variables or Kerberos config are included application flink conf, then one of
> decorators will be enabled. TM Pod will mount on config maps or secrets that
> are not created yet.
> Thus, we should help user to disable these two Decorators by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
