scale

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Recently reproduce many time in CI

https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_unit_test/detail/tidb_ghpr_unit_test/38976/pipeline/

[2022-03-04T03:58:22.683Z] ------------------------

What version of Knative?

v1.0 at least

Expected Behavior

When creating a Revision with a pod which exits immediately, the Revision should (fairly quickly) report that Ready is False and terminate the Pods.

Actual Behavior

The pods stick around

• oceanbase/oceanbase#486
• oceanbase/oceanbase#483
• oceanbase/oceanbase#482
• oceanbase/oceanbase#481
• oceanbase/oceanbase#480
• oceanbase/oceanbase#477
• oceanbase/oceanbase#476
• https://github.com/oceanbas

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

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