[
https://issues.apache.org/jira/browse/FLINK-15682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019883#comment-17019883
]
Yang Wang commented on FLINK-15682:
-----------------------------------
[~yuzhaojing] Please update the log4j configuration to see why the pods came
across with errors[1]. I guess your service account[2] do not have enough
permission.
[1].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#log-files]
[2].
[https://ci.apache.org/projects/flink/flink-docs-master/ops/deployment/native_kubernetes.html#rbac]
> Flink native kubernetes Could not run
> -------------------------------------
>
> Key: FLINK-15682
> URL: https://issues.apache.org/jira/browse/FLINK-15682
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Reporter: yuzhaojing
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Attachments: image-2020-01-21-10-37-42-248.png,
> image-2020-01-21-13-29-18-903.png, image-2020-01-21-13-30-59-731.png,
> image-2020-01-21-14-24-46-752.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently,native kubernetes use exec /bin/bash -c java_command to start
> jobmanager and taskmanager.but there are $Flink_ClassPath in
> java_command,when use exec $@,this env can't be parse.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
