scale

/area API
/kind good-first-issue

Describe the feature

For flagged fields like kubernetes.podspec-fieldref the validation should include the name of the feature flag to toggle in the error message it surfaces. The validation logic is roughly here: https://github.com/knative/serving/blob/644798277d9fe6715e4f638281141356df46d7e1/pkg/apis/serving/k8s_validation.go#L246

Describe the issue

For every master merge, we create a new release. We also generate docs and create PR for every master merge.

We want to avoid release workflow in case of docs or boilerplate PR.

What if we do not do this?

We have extra releases that only have docs changes, which isn't desirable.

Related component(s)

Flytectl

Are you sure this issue hasn't b

Describe the bug

Our standard is to use XML comments on public methods as these provides documentation on a help request. The ASB Transport needs this work

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