Also you can check if the configs are updated properly in the ConfigMap. It should be auto-populated when you reinstall it from Helm as Gyula suggested. *kubernetes.operator.watched.namespaces: ns1, ns2, ...*
On Tue, Aug 23, 2022 at 5:37 PM Gyula Fóra <gyula.f...@gmail.com> wrote: > Hi! > > From your logs I see: > > Configuring operator to watch the following namespaces: [JOSDK_ALL_NAMESPACES] > This means that the operator is not configured correctly for the watched > namespaces. After you change the helm values you might have to reinstall the > operator. > > Cheers, > Gyula > > > On Mon, Aug 22, 2022 at 5:16 PM Sigalit Eliazov <e.siga...@gmail.com> > wrote: > >> Hi, >> we are trying to start a flink operator with a specific namespace. >> flink-operator version: 1.1.0 >> >> we set the following parameter : watchNamespaces: ["my-namespace"] >> >> The operator fails during installation with the following error >> >> *Caused by: io.fabric8.kubernetes.client.KubernetesClientException: * >> >> *Failure executing: GET at: >> https://10.96.0.1/apis/flink.apache.org/v1beta1/flinkdeployments >> <http://10.96.0.1/apis/flink.apache.org/v1beta1/flinkdeployments>. Message: >> Forbidden!Configured service account doesn't have access. * >> >> *Service account may have been revoked. flinkdeployments.flink.apache.org >> <http://flinkdeployments.flink.apache.org> is forbidden: User >> "system:serviceaccount:my-namespace:flink-operator" * >> >> *cannot list resource "flinkdeployments" in API group "flink.apache.org >> <http://flink.apache.org>" at the cluster scope: RBAC: >> clusterrole.rbac.authorization.k8s.io >> <http://clusterrole.rbac.authorization.k8s.io> "psp:privileged" not found.* >> >> >> we would expect that the list operation will take into consideration the >> namespace as well. >> Attached log file >> Is there any other configuration required? >> >> Thanks >> Sigalit >> >
