Mate Czagany created FLINK-32652:
------------------------------------
Summary: Operator cannot scale standalone deployments in reactive
mode
Key: FLINK-32652
URL: https://issues.apache.org/jira/browse/FLINK-32652
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.6.0
Reporter: Mate Czagany
After we upgraded the Fabric8 Kubernetes Client to 6.7.0 the operator can no
longer scale standalone deployments in reactive mode because it uses the
"deployments/scale" API instead of patching the deployment since this commit:
[https://github.com/fabric8io/kubernetes-client/commit/c4d3dd14c6ba7261fe4646636d277cba1c2122a2]
We will get the following error:
{code:java}
org.apache.flink.kubernetes.operator.exception.ReconciliationException:
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET
at:
https://10.96.0.1:443/apis/apps/v1/namespaces/flink/deployments/basic-reactive-example-taskmanager/scale.
Message: Forbidden!Configured service account doesn't have access. Service
account may have been revoked. deployments.apps
"basic-reactive-example-taskmanager" is forbidden: User
"system:serviceaccount:flink:flink-operator" cannot get resource
"deployments/scale" in API group "apps" in the namespace "flink". {code}
The fix is easy, we just need to add "deployments/scale" to the ClusterRole we
create, I'll create a PR soon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
