You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer used their own auto-gen tooling to generate eraser configmap while by mistake, a invalid key tag:v1.1.0request with null value was generated. Moreover, the mem and cpu changes supposed to be under request were put under image which caused eraser still use default request values.
If we have kinda validations to check those key/properties once config yaml was applied, report like
tag:v1.1.0request is an invalid key under image
men is an invalid key under image
cpu is an invalid key under image
then it must help us debug and find customer's configuration error earlier?
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Is that possible to add key/property validation check in
eraser_controller_manager_config
?For example, if I have piece of configmap like
Customer used their own auto-gen tooling to generate eraser configmap while by mistake, a invalid key
tag:v1.1.0request
withnull
value was generated. Moreover, themem
andcpu
changes supposed to be underrequest
were put underimage
which caused eraser still use default request values.If we have kinda validations to check those key/properties once config yaml was applied, report like
tag:v1.1.0request
is an invalid key underimage
men
is an invalid key underimage
cpu
is an invalid key underimage
then it must help us debug and find customer's configuration error earlier?
The text was updated successfully, but these errors were encountered: