Dennis-Mircea commented on PR #1070: URL: https://github.com/apache/flink-kubernetes-operator/pull/1070#issuecomment-4177888566
> Why are we changing this? We actually want to get rid of this config eventually, so it _should_ be deprecated. > > Min/max/target should be used by the users, documentation is still available in older versions when really necessary. > > In my view this PR should be closed Thank you for the comment, @gyfora! I understand the intention to eventually remove this config, and I agree that users should rely on the min/max/target utilization knobs going forward. The issue I’m trying to address is that the current Autoscaler documentation still references this boundary property, without pointing readers to the intended replacement (min & max thresholds) or explaining the migration path. If the plan is to keep deprecated this configuration, I suggest we first update the Autoscaler docs to: - remove (or clearly mark as deprecated) the boundary reference, and - explicitly document the recommended usage of min & max utilization (and how it maps to the previous behavior). Happy to adjust the PR accordingly (e.g., convert it into a docs-only change) if you think that’s the right direction. Please let me know your opinion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
