OCPBUGS-56264: Align ROSA logo with managed-cluster-config

[logonoff]

before:

after:

code review:
/assign @rhamilto

/backport release-4.19

[openshift-ci-robot]

@logonoff: This pull request references Jira Issue OCPBUGS-56264, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

before:

after:

code review:
/assign @rhamilto

/backport release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[logonoff]

/jira refresh

[openshift-ci-robot]

@logonoff: This pull request references Jira Issue OCPBUGS-56264, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [logonoff]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rhamilto]

Per brand, the logo should be the three line version. The problem is, whoever is branding ROSA is using a custom branding option and not the option within console.

[logonoff]

Per brand, the logo should be the three line version. The problem is, whoever is branding ROSA is using a custom branding option and not the option within console.

That is set here: https://github.com/openshift/managed-cluster-config/blob/master/source/html/rosa/rosa-brand-logo.svg

I thought that the current, two-line ROSA logo used in production would be aligned with brand. However, if the three-line one is the preferred logo then we can close this PR

[logonoff]

I opened a PR to use the console-provided logo: openshift/managed-cluster-config#2426

[openshift-ci]

@logonoff: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@logonoff: This pull request references Jira Issue OCPBUGS-56264. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

before:

after:

code review:
/assign @rhamilto

/backport release-4.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.