[
https://issues.apache.org/jira/browse/FLINK-33519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17788241#comment-17788241
]
chaoran.su edited comment on FLINK-33519 at 11/21/23 3:51 AM:
--------------------------------------------------------------
actually, this is because of flink-kubernetes lib's logic, which will modify
the configuration of "security.kerberos.login.keytab", which I think this
should be clearly wrote in flink operator doc, to explain this error could be
solved by modified the path in this "security.kerberos.login.keytab"
configuration to "
/opt/kerberos/kerberos-keytab". Or just create a soft link from source dir to
this dir.
I this add doc will be fined, there is not right place to modified the code of
flink operator to solved this problem.
was (Author: JIRAUSER301214):
actually, this is because of flink-kubernetes lib's logic, which will modify
the configuration of "security.kerberos.login.keytab", which I think this
should be clearly wrote in flink operator doc, to explain this error could be
solved by modified the path in this "security.kerberos.login.keytab"
configuration to "
/opt/kerberos/kerberos-keytab". Or just create a soft link from source dir to
this dir.
> standalone mode could not create keytab secret
> ----------------------------------------------
>
> Key: FLINK-33519
> URL: https://issues.apache.org/jira/browse/FLINK-33519
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.3.0, kubernetes-operator-1.4.0,
> kubernetes-operator-1.3.1, kubernetes-operator-1.5.0,
> kubernetes-operator-1.6.0, kubernetes-operator-1.6.1
> Reporter: chaoran.su
> Priority: Major
>
> when standalone build cluster, and configuration with
> security.kerberos.login.* configurations.
> flink-kubernetes module will modify the path of
> security.kerberos.login.keytab configuration to
> /opt/kerberos/kerberos-keytab, and then create secret for job manager. the
> secret data from operator pod's keytab file.
> after job manager created, creating task manager process will find the keytab
> file from the location from security.kerberos.login.keytab configuration,
> then it throws a exception says keytabs file not find.
> the bug is because of the configuration modified once, and reused it when
> create tm. Native mode didn't exist this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
