Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Red Hat branding in fresh install on OpenStack #2105

Open
alexzose opened this issue Jan 31, 2025 · 2 comments
Open

Red Hat branding in fresh install on OpenStack #2105

alexzose opened this issue Jan 31, 2025 · 2 comments

Comments

@alexzose
Copy link

Installed OKD SCOS 4.17.0-okd-scos.2 with IPI on OpenStack. The oauth-openshift page has Red Hat logo / branding.

The weird thing is that we also had a FCOS variant version 4.15 installed on the same OpenStack environment, which we updated to 4.17 SCOS and the oauth-openshift page does not have this issue.

@BeardOverflow
Copy link

It is already resolved for 4.18 version, but was not backported to 4.16/4.17 releases.
https://issues.redhat.com/browse/OKD-214
openshift/console-operator#896

As workaround, you can configure the branding avoiding console-operator:

apiVersion: v1
kind: ConfigMap
metadata:
  annotations:
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
  name: console-config
  namespace: openshift-config-managed
data:
  console-config.yaml: |
    kind: ConsoleConfig
    apiVersion: console.openshift.io/v1
    customization:
      branding: okd
      documentationBaseURL: https://docs.okd.io/4.17/

@alexzose
Copy link
Author

It worked just fine, thanks.

Indeed, in our other cluster that we updated from FCOS to SCOS, the ConfigMap was present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants