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

Please check the FAQ documentation before raising an issue

Please check the old issues before raising an issue in case someone has asked the same question that you are asking.

Describe the bug (must be provided)
in file deps/oblib/src/lib/atomic/ob_atomic.h
macro ATOMIC_FAA double defined

A clear and concise description of what the bug is.

**Your Environments (__must

Describe the Issue

• Currently, we have old documentation in gh-pages but now we are not using the gh-pages for documentation and Add documentation for helm in gh-pages README
  https://github.com/flyteorg/flyte/tree/gh-pages

What if we do not do this?

Related component
Either Specific / all

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