Currently, the flink-kubernetes-operator is using Flink native K8s integration[1], which means Flink ResourceManager will dynamically allocate TaskManager on demand. So the users do not need to specify the replicas of TaskManager.
Just like Gyula said, one possible solution to make "kubectl scale" work is to change the parallelism of Flink job. If the standalone mode[2] is introduced in the operator, then it is also possible to directly change the replicas of TaskManager pods. [1]. https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/deployment/resource-providers/native_kubernetes/ [2]. https://cwiki.apache.org/confluence/display/FLINK/FLIP-225%3A+Implement+standalone+mode+support+in+the+kubernetes+operator Best, Yang Gyula Fóra <gyf...@apache.org> 于2022年5月7日周六 04:26写道： > Hi Jay! > > Interesting question/proposal to add the scale-subresource. > > I am not an expert on this area but we will look into this a little and > give you some feedback and see if we can incorporate something into the > upcoming release if it makes sense. > > On a high level there is not a single replicas value for a > FlinkDeployment that would be easy to map, but maybe we could use the > parallelism value for this purpose for Applications/Session jobs. > > Cheers, > Gyula > > On Fri, May 6, 2022 at 8:04 PM Jay Ghiya <ghiya6...@gmail.com> wrote: > >> Hi Team, >> >> >> I have been experimenting the Flink Kubernetes operator. One of the >> biggest miss that we have is it does not support scale sub resource as of >> now to support reactive scaling. Without that commercially it becomes very >> difficult for products like us who have very varied loads for every hour. >> >> >> >> Can I get some direction on the same to contribute on >> https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#scale-subresource >> for >> our Kubernetes operator crd? >> >> I have been a hard time reading -> >> *https://github.com/apache/flink-kubernetes-operator/blob/main/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml >> <https://github.com/apache/flink-kubernetes-operator/blob/main/helm/flink-kubernetes-operator/crds/flinkdeployments.flink.apache.org-v1.yml> >> to >> figure out the replicas, status,label selector json path of task >> manager? It may be due to lack of my knowledge so sense of direction will >> help me.* >> >> *-Jay* >> *GEHC* >> >
