HIVE-2366 is currently asking Hive to lift some ClusterVersion status properties, including conditionalUpdates from ClusterVersion up towards OCM. conditionalUpdates doesn't touch on either supported but not recommended or known issues directly, but it does include a risks structure and Recommended conditions. Do we want to ask Hive to translate to different wording? Or do we want Hive to preserve the ClusterVersion structure, and have OCM or some later level translate to different wording? And I guess if we were really motivated for future-consistency at the expense of some existing-client churn, we could teach ClusterVersion status about a new structure/conditions, and deprecate (but maybe never remove?) the existing API. But basically, the existing ClusterVersion API isn't on-brand with this Epic's new UX wording, and this ticket is about picking where in that API-to-UX piping we want to have the rebranding.