Skip to content

Conversation

logonoff
Copy link
Member

What type of PR is this?

(bug/feature/cleanup/documentation)

bugfix + cleanup

What this PR does / why we need it?

Removes the rosa-brand-logo.svg custom logo in favor of setting the brand to ROSA.

This fixes an issue with the contrast of the ROSA logo on OpenShift 4.19+, where the masthead can change background colours from light to dark.

Instead of using the new custom logo API, which would contain new schema that is not recognized by older versions of OpenShift, changing the value of brand achieves the same effect (i.e., the title and logo are changed).

Any future updates that are needed to the ROSA logo can be made in the openshift/console repo.

Which Jira/Github issue(s) this PR fixes?

https://issues.redhat.com/browse/OCPBUGS-55803

Special notes for your reviewer:

Is there a way to update the oauth-templates versions of OpenShift newer than 4.19?

A new version of oauth-templates was released which contains the PatternFly 6 changes made in 4.19 and is ready for consumption by this repo

Pre-checks (if applicable):

  • Tested latest changes against a cluster

  • Included documentation changes with PR

  • If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

    matchExpressions:
    - key: api.openshift.com/fedramp
      operator: NotIn
      values: ["true"]

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 15, 2025
@openshift-ci-robot
Copy link

@logonoff: This pull request references Jira Issue OCPBUGS-55803, 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:

What type of PR is this?

(bug/feature/cleanup/documentation)

bugfix + cleanup

What this PR does / why we need it?

Removes the rosa-brand-logo.svg custom logo in favor of setting the brand to ROSA.

This fixes an issue with the contrast of the ROSA logo on OpenShift 4.19+, where the masthead can change background colours from light to dark.

Instead of using the new custom logo API, which would contain new schema that is not recognized by older versions of OpenShift, changing the value of brand achieves the same effect (i.e., the title and logo are changed).

Any future updates that are needed to the ROSA logo can be made in the openshift/console repo.

Which Jira/Github issue(s) this PR fixes?

https://issues.redhat.com/browse/OCPBUGS-55803

Special notes for your reviewer:

Is there a way to update the oauth-templates versions of OpenShift newer than 4.19?

A new version of oauth-templates was released which contains the PatternFly 6 changes made in 4.19 and is ready for consumption by this repo

Pre-checks (if applicable):

  • Tested latest changes against a cluster

  • Included documentation changes with PR

  • If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

    matchExpressions:
    - key: api.openshift.com/fedramp
      operator: NotIn
      values: ["true"]

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 openshift-ci bot requested review from apahim and boranx May 15, 2025 17:38
Copy link
Contributor

openshift-ci bot commented May 15, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: logonoff
Once this PR has been reviewed and has the lgtm label, please assign xiaoyu74 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

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

@logonoff
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 15, 2025
@openshift-ci-robot
Copy link

@logonoff: This pull request references Jira Issue OCPBUGS-55803, 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 openshift-ci bot requested a review from yapei May 15, 2025 17:39
@logonoff logonoff changed the title OCPBUGS-55803: Use console-provided ROSA branding OCPBUGS-56264, OCPBUGS-55803: Use console-provided ROSA branding May 20, 2025
@openshift-ci-robot
Copy link

@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

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

This pull request references Jira Issue OCPBUGS-55803, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

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

In response to this:

What type of PR is this?

(bug/feature/cleanup/documentation)

bugfix + cleanup

What this PR does / why we need it?

Removes the rosa-brand-logo.svg custom logo in favor of setting the brand to ROSA.

This fixes an issue with the contrast of the ROSA logo on OpenShift 4.19+, where the masthead can change background colours from light to dark.

Instead of using the new custom logo API, which would contain new schema that is not recognized by older versions of OpenShift, changing the value of brand achieves the same effect (i.e., the title and logo are changed).

Any future updates that are needed to the ROSA logo can be made in the openshift/console repo.

Which Jira/Github issue(s) this PR fixes?

https://issues.redhat.com/browse/OCPBUGS-55803

Special notes for your reviewer:

Is there a way to update the oauth-templates versions of OpenShift newer than 4.19?

A new version of oauth-templates was released which contains the PatternFly 6 changes made in 4.19 and is ready for consumption by this repo

Pre-checks (if applicable):

  • Tested latest changes against a cluster

  • Included documentation changes with PR

  • If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

    matchExpressions:
    - key: api.openshift.com/fedramp
      operator: NotIn
      values: ["true"]

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 added 2 commits May 22, 2025 11:29
Removes the `rosa-brand-logo.svg` custom logo in favor of setting the `brand` to `ROSA`.

This fixes an issue with the contrast of the ROSA logo on OpenShift 4.19+, where the masthead can change background colours from light to dark.

Instead of using the [new custom logo API](openshift/enhancements#1753), which would contain new schema that is not recognized by older versions of OpenShift, changing the value of `brand` achieves the same effect (i.e., the title and logo are changed).

Any future updates that are needed to the ROSA logo can be made in the openshift/console repo.
@logonoff logonoff force-pushed the OCPBUGS-55803-logo branch from 09545b6 to 7309da8 Compare May 22, 2025 15:30
Copy link
Contributor

openshift-ci bot commented May 22, 2025

@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
Copy link

@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.

This pull request references Jira Issue OCPBUGS-55803. 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:

What type of PR is this?

(bug/feature/cleanup/documentation)

bugfix + cleanup

What this PR does / why we need it?

Removes the rosa-brand-logo.svg custom logo in favor of setting the brand to ROSA.

This fixes an issue with the contrast of the ROSA logo on OpenShift 4.19+, where the masthead can change background colours from light to dark.

Instead of using the new custom logo API, which would contain new schema that is not recognized by older versions of OpenShift, changing the value of brand achieves the same effect (i.e., the title and logo are changed).

Any future updates that are needed to the ROSA logo can be made in the openshift/console repo.

Which Jira/Github issue(s) this PR fixes?

https://issues.redhat.com/browse/OCPBUGS-55803

Special notes for your reviewer:

Is there a way to update the oauth-templates versions of OpenShift newer than 4.19?

A new version of oauth-templates was released which contains the PatternFly 6 changes made in 4.19 and is ready for consumption by this repo

Pre-checks (if applicable):

  • Tested latest changes against a cluster

  • Included documentation changes with PR

  • If this is a new object that is not intended for the FedRAMP environment (if unsure, please reach out to team FedRAMP), please exclude it with:

    matchExpressions:
    - key: api.openshift.com/fedramp
      operator: NotIn
      values: ["true"]

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 logonoff deleted the OCPBUGS-55803-logo branch May 26, 2025 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants