[ 
https://issues.apache.org/jira/browse/FLINK-33094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lee SeungMin updated FLINK-33094:
---------------------------------
    Summary: kubernetes.decorator.kerberos-mount.enabled does not work  (was: 
KUBERNETES_KERBEROS_MOUNT_DECORATOR_ENABLED(kubernetes.decorator.kerberos-mount.enabled)
 not works)

> kubernetes.decorator.kerberos-mount.enabled does not work
> ---------------------------------------------------------
>
>                 Key: FLINK-33094
>                 URL: https://issues.apache.org/jira/browse/FLINK-33094
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes, Kubernetes Operator
>            Reporter: Lee SeungMin
>            Priority: Minor
>         Attachments: image-2023-09-16-00-08-56-204.png, 
> image-2023-09-16-00-12-12-793.png
>
>
> I deployed `basic-example` using flink-kubernetes-operator(v1.5.0)
> ([Quick Start | Apache Flink Kubernetes 
> Operator)|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.5/docs/try-flink-kubernetes-operator/quick-start/]
>  
> I do not need to mount kerberos (keytab), so I set 
> `kubernetes.decorator.kerberos-mount.enabled` as `false`
> And checked that above option set as `false` in log of job manager and task 
> manager.
> !image-2023-09-16-00-08-56-204.png!
>  
> Then as I understand, when `kubernetes.decorator.kerberos-mount.enabled` is 
> `false`, it should not create secret.
> But It create secret.
> !image-2023-09-16-00-12-12-793.png!
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to