I'm increasing severity, as we want to have this fixed before the release, otherwise we would be forced to maintain an API with a typo.
(In reply to Martin Bukatovic from comment #2) > I'm increasing severity, as we want to have this fixed before the release, > otherwise we would be forced to maintain an API with a typo. AFAICT, The release is TechPreview, and as such API backward compatibility is not a concern. Hence we should not be forced to maintain this API with the typo in the status output field, which further is not part of the API spec in general. (i.e it is not a Condition and its reason as such, but a status string). I am not stating to not take a fix into the release, but just correcting my understanding of the severity change.