wangyang0918 removed a comment on pull request #91:
URL: 
https://github.com/apache/flink-kubernetes-operator/pull/91#issuecomment-1074641011


   ```
   2022-03-21 18:17:17,693 i.j.o.a.c.ExecutorServiceManager [DEBUG] Initialized 
ExecutorServiceManager executor: class java.util.concurrent.ThreadPoolExecutor, 
timeout: 10
   Error: Exception in thread "main" 
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET 
at: 
https://10.96.0.1/apis/apiextensions.k8s.io/v1/customresourcedefinitions/flinkdeployments.flink.apache.org.
 Message: Forbidden!Configured service account doesn't have access. Service 
account may have been revoked. customresourcedefinitions.apiextensions.k8s.io 
"flinkdeployments.flink.apache.org" is forbidden: User 
"system:serviceaccount:default:flink-operator" cannot get resource 
"customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster 
scope.
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:682)
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:661)
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:610)
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:555)
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:[518](https://github.com/apache/flink-kubernetes-operator/runs/5632398750?check_suite_focus=true#step:9:518))
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:487)
        at 
io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleGet(OperationSupport.java:457)
        at 
io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleGet(BaseOperation.java:698)
        at 
io.fabric8.kubernetes.client.dsl.base.BaseOperation.getMandatory(BaseOperation.java:184)
        at 
io.fabric8.kubernetes.client.dsl.base.BaseOperation.get(BaseOperation.java:151)
        at 
io.fabric8.kubernetes.client.dsl.base.BaseOperation.get(BaseOperation.java:83)
        at 
io.javaoperatorsdk.operator.processing.Controller.start(Controller.java:178)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown 
Source)
        at 
java.base/java.util.HashMap$ValueSpliterator.forEachRemaining(Unknown Source)
        at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
        at java.base/java.util.stream.ForEachOps$ForEachTask.compute(Unknown 
Source)
        at java.base/java.util.concurrent.CountedCompleter.exec(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask.doInvoke(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask.invoke(Unknown Source)
        at 
java.base/java.util.stream.ForEachOps$ForEachOp.evaluateParallel(Unknown Source)
        at 
java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(Unknown 
Source)
        at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
        at java.base/java.util.stream.ReferencePipeline.forEach(Unknown Source)
        at java.base/java.util.stream.ReferencePipeline$Head.forEach(Unknown 
Source)
        at 
io.javaoperatorsdk.operator.Operator$ControllerManager.start(Operator.java:164)
        at io.javaoperatorsdk.operator.Operator.start(Operator.java:82)
        at 
org.apache.flink.kubernetes.operator.FlinkOperator.main(FlinkOperator.java:84)
   ```
   @gyfora Maybe we could add the following codes in 
`e2e-tests/utils.sh#debug_and_show_logs` to print the actual RBAC.
   
   ```
       kubectl get serviceaccount flink-operator -o yaml
       kubectl get clusterrole flink-operator -o yaml
       kubectl get clusterrolebinding flink-operator-cluster-role-binding -o 
yaml
   ```


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to