[
https://issues.apache.org/jira/browse/FLINK-35105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844136#comment-17844136
]
Rui Fan commented on FLINK-35105:
---------------------------------
Merged to main(1.9.0) via: 249a6945aaa847a506c42111d7332ad072578095
> Support setting default Autoscaler options at autoscaler standalone level
> -------------------------------------------------------------------------
>
> Key: FLINK-35105
> URL: https://issues.apache.org/jira/browse/FLINK-35105
> Project: Flink
> Issue Type: Sub-task
> Components: Autoscaler
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.9.0
>
>
> Currently, autoscaler standalone doesn't support set [autoscaler
> options|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.8/docs/operations/configuration/#autoscaler-configuration].
> We must set them at job level when we use autoscaler standalone. It's not
> convenient if platform administrator wanna change the default value for some
> autoscaler options, such as:
> * job.autoscaler.enabled
> * job.autoscaler.metrics.window
> * etc
> This Jira supports setting Autoscaler options at autoscaler standalone level,
> it's similar with flink kubernetes operator.
> The autoscaler options of autoscaler standalone will be as the base
> configuration, and the configuration at job-level can override the default
> value provided in the autoscaler standalone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
