scale

Enhancement

[2022-02-14T04:12:14.746Z] ----------------------------------------------------------------------
[2022-02-14T04:12:14.746Z] FAIL: db_test.go:7069: testSerialDBSuite.TestModifyColumnTypeWhenInterception
[2022-02-14T04:12:14.746Z] 
[2022-02-14T04:12:14.746Z] db_test.go:7124:
[2022-02-14T04:12:14.746Z]     c.Assert(checkMiddleWarningCount, Equals, true)
[2022-02-14T04:12:

/area API
/area autoscale
/kind cleanup

Actual Behavior

The max-scale and min-scale annotation has been introduced in knative/serving#12103 alignment. The client was using those names, but recently this changed to the inverse - knative/client#958. This leads to confusion on docs, and UX as seen in: https://github.com/knative/docs/iss

Describe your question

平台：mac m1 arm64
容器平台： docker desktop V4.5.0
docker版本：Server Version: 20.10.12 Storage Driver: overlay2
运行镜像：oceanbase/oceanbase-ce standalone-3.1.3
启动命令：docker run -p 2881:2881 --name obstandalone --platform linux/amd64 -e MINI_MODE=1 -d oceanbase/oceanbase-ce:standalone-3.1.3

启动过程中的问题：
启动执行 docker logs obstandalone 有以下信息

generate boot.yaml ...
/root/boot

Describe the issue

Oftentimes, for a variety of reasons, users will see a stack trace like the following when running pyflyte run or registering a Flyte entity through FlyteRemote.

Traceback (most recent call last):
  File "/fn/bin/flyte-cli", line 8, in <module>
    sys.exit(_flyte_cli())
  File "/fn/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return 

Is your feature request related to a problem? Please describe.
I would like to know how Brighter reacts if it receives messages from other systems.

Describe the solution you'd like
Would like to know if you can rely on default behavior or if any additional message headers are needed

Is your feature request related to a problem? Please describe.

Updating escalator config currently requires a pod restart. We should update escalator to automatically read new config upon changing on disk.

Describe the solution you'd like

Check for changes in nodegroup config before each run. If safe to do so, run with the new config.

*Describe alternatives you've considered