Open gtully opened 4 months ago
Non fatal sounds good to me.
actually thinking more, it is an invalid CR, and we know before we try and update, so we can make it a fatal condition. A variation of the ValidCondition with an unmatched resource template at [index] reason.
With the resource template, the match criteria can be specific and match on a name. however if that name is incorrect, there is no validation, the template is ignored. in that case, it would be nice to report an UnmatchedResourceTempate Condition in the Status.
not sure if this condition should mean Ready=false, it is indeed non fatal. lets discuss.