Created attachment 1511349 [details] screenshot Description of problem: *This is not how we are telling customers to deploy* but if a customer would go to the OCP service catalog and try to deploy kubevirt from there, he will see a version dropdown list with one value - 0.9.3 Version-Release number of selected component (if applicable): kubevirt-apb-v3.11-14 How reproducible: 100% Steps to Reproduce: 1. import the hidden apb 2. go to ocp console and double click the kubevirt-apb 3. see 'version' param Actual results: only available version is 0.9.3 Expected results: d/s v1.3.0 version Additional info:
0.9.3 is used to select the offline downstream templates so we'll use to keep it. So this is missing a downstream translation. It's not ideal, but tag is what will reflect the version.
downstream translation for this would be a large change based on how we're pulling in the templates now. I think that why this was deprioritized.