kube-state-metrics icon indicating copy to clipboard operation
kube-state-metrics copied to clipboard

Take field modifications into account in CRS configurations

Open rexagod opened this issue 1 year ago • 1 comments

What happened: Suppose a CR that may append fields conditionally, for eg. VPAs. For the the transient duration that it takes for the autoscaling pipeline to provide recommendations, the condition field is nil, and thus, as a result, any configurations depending on this field will cause KSM to log errors repeatedly until those fields are appended.

What you expected to happen: No error logs, and even if there were, should point out exactly which resource was causing the transient error(s) (some VPAs may be initialized sooner or later than others).

How to reproduce it (as minimally and precisely as possible): Enable KSM and use the CRS featureset on VPAs.

rexagod avatar Dec 10 '23 17:12 rexagod

/triage accepted /assign @rexagod

logicalhan avatar Dec 14 '23 17:12 logicalhan