[
https://issues.apache.org/jira/browse/FLINK-32723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782593#comment-17782593
]
Rui Fan commented on FLINK-32723:
---------------------------------
FLIP-334 (FLINK-32723) wants to decouple autoscalers and kubernetes operators
and support autoscaler standalone. FLINK-33099 is supporting the autoscaler
standalone, it works as a separate process and support a single flink cluster.
Flink users can play autoscaler and in-place rescale with flink-1.18 directly
without kubernetes.
Based on it, I think once FLINK-33099 is merged, we almost met our initial
expectations of FLIP-334.
In addition, kubernetes operator 1.7 will be released soon, and the rest
improvements related to autoscaler or autoscaler-standalone can be done in the
kubernetes operator 1.8 or later. So I create FLINK-33452 to follow them.
Hopefully, autoscaler standalone will be production-ready in a future release.
> FLIP-334 : Decoupling autoscaler and kubernetes and support the Standalone
> Autoscaler
> -------------------------------------------------------------------------------------
>
> Key: FLINK-32723
> URL: https://issues.apache.org/jira/browse/FLINK-32723
> Project: Flink
> Issue Type: New Feature
> Components: Autoscaler, Kubernetes Operator
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
>
> This is an umbrella jira for decoupling autoscaler and kubernetes.
> https://cwiki.apache.org/confluence/x/x4qzDw
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
