huyuanfeng2018 commented on PR #921: URL: https://github.com/apache/flink-kubernetes-operator/pull/921#issuecomment-2576559250
Thanks @1996fanrui @gyfora for the reply Well, let me summarize our conclusion, * we need to remove the boundary parameter in the future (deprecate now), So there is no need to rename it now * default min/max need to be derived from target Then the logic for determining the default value of min/max is ： now（boundary exist） : `max = upper.boundary+ target , min = target- upper.boundary` future（boundary remove） : `max = 0.3 + target , min = target- 0.3`, `0.3` is a static value I don’t know if there is anything wrong with my understanding. -- 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: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
