Description of problem: The Kubevirt Web UI is currently branded with OKD Version-Release number of selected component (if applicable): v1.3.0 How reproducible: 100% Steps to Reproduce: 1. login to https://kubevirt-web-ui.cloudapps.example.com 2. 3. Actual results: OKD branded Expected results: Openshift branding Additional info:
For consistency, needs to use OpenShift logo in the same way as the OpenShift Console. Short term fix in kubevirt-web-ui, long term fix is merging into OpenShift console.
Fix on web-ui side: https://github.com/kubevirt/web-ui/pull/140 Operator supports branding: https://github.com/kubevirt/web-ui-operator/pull/22 To change branding, set the value in custom resource for the Kubevirt Web UI Operator: - spec.branding=openshiftvirt For 1.4, the deployment will be handled via operator (as mentioned above). Anyway, it is recently unclear, how to operator will be deployed or initiated. As a next step, either - downstream web-ui operator build will contain properly pre-set CR - or 1.4 documentation will need to reflect setting the custom resource - or the operator of operators (OLM) will handle that
if installed using operator, the branding is there
I installed the web ui 1.4.0-9 via operator, it still branded with okd.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0417