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 <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
