You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/04/07 06:59:00 UTC
[jira] [Closed] (FLINK-27098) The session job controller should create FlinkDeployment informer event source with namespace definition
[ https://issues.apache.org/jira/browse/FLINK-27098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Wang closed FLINK-27098.
-----------------------------
Resolution: Fixed
> The session job controller should create FlinkDeployment informer event source with namespace definition
> --------------------------------------------------------------------------------------------------------
>
> Key: FLINK-27098
> URL: https://issues.apache.org/jira/browse/FLINK-27098
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Xin Hao
> Assignee: Xin Hao
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.0.0
>
>
> The below error will occur if we deploy the operator with a namespaced scope and submit a session job.
>
> {code:java}
> [WARN ] Error starting org.apache.flink.kubernetes.operator.controller.FlinkSessionJobController$1@96a75da
> io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://10.16.0.1/apis/flink.apache.org/v1alpha1/namespaces/flink-operator/flinkdeployments. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. flinkdeployments.flink.apache.org is forbidden: User "system:serviceaccount:flink-operator:flink-operator" cannot list resource "flinkdeployments" in API group "flink.apache.org" in the namespace "flink-operator". {code}
> This error comes from the creation of the FlinkDeployment informer event source.
> I just submitted a PR to fix this, https://github.com/apache/flink-kubernetes-operator/pull/157
--
This message was sent by Atlassian Jira
(v8.20.1#820001)