You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "chaoran.su (Jira)" <ji...@apache.org> on 2023/11/10 12:00:00 UTC

[jira] [Created] (FLINK-33519) standalone mode could not create keytab secret

chaoran.su created FLINK-33519:
----------------------------------

             Summary: 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.6.1, kubernetes-operator-1.6.0, kubernetes-operator-1.5.0, kubernetes-operator-1.3.1, kubernetes-operator-1.4.0, kubernetes-operator-1.3.0
            Reporter: chaoran.su


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)