You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/04/28 09:13:16 UTC

[GitHub] [flink-kubernetes-operator] mnuttall commented on pull request #186: [FLINK-27425] Default job service account needs access to services to work with Kafka

mnuttall commented on PR #186:
URL: https://github.com/apache/flink-kubernetes-operator/pull/186#issuecomment-1111955950

   Hi @morhidi, after further testing, I only see this problem in a very limited situation:
   
   - create a session cluster using a FlinkDeployment with no `spec.job` stanza
   - exec into the cluster pod
   - run bin/sql-client.sh
   - create a TABLE backed by a kafka topic and execute a SELECT against it
   
   At this point, the RBAC error shown above appears inline within the sql-client, but no exceptions appear either within the sql-client or the pod logs.
   
   However, the Role does not need to be changed in order for the same to work on an application cluster with the SQL submitted via the Table API.
   
   Should it be possible to exec into a session cluster's job manager and run and submit jobs via the sql-client? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org