Hi, I have a few questions about the Flink OSS Kubernetes operator. Apologies if they’re basic.
1. It seems like the auto-scaler logic is triggered as part of the operator reconciliation loop <https://github.com/apache/flink-kubernetes-operator/blob/main/flink-kubernetes-operator/src/main/java/org/apache/flink/kubernetes/operator/reconciler/deployment/AbstractFlinkResourceReconciler.java#L132>. Does this mean the auto-scaler is expected to be applied as part of job deployment or when the state of any of the watched K8s objects is changed over time. 2. From the implementation, it seems like OSS flink K8s operator changes the parallelism of flink-operators in the job depending upon processing rate and catchup rate configurations. Just wondering if these parallelism changes are preserved across job restarts/deployments or if the parallelism configured in the job for different flink operators is used upon restart. 3. Just wondering how the auto-scaler checks if the kubernetes cluster has sufficient capacity before increasing the parallelism of flink operators. 4. Are users expected to use HPA or VPA in conjunction with the auto-scaling module in Flink K8s operator. Or are these two unrelated to each other? Thanks.
