Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-33519

standalone mode could not create keytab secret

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 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
    • None
    • Kubernetes Operator
    • None

    Description

      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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            richard.su chaoran.su
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: