CONSOLE-4404,CONSOLE-4062: Add the ability to specify second logo, favicons #14749

Mylanos · 2025-02-10T17:20:36Z

After:

Screen.Recording.2025-02-10.at.18.06.06.mov

bridge command used for testing:

./bin/bridge --custom-logo-files Dark=frontend/public/imgs/okd-logo-dark.svg,Light=frontend/public/imgs/okd-logo-light.svg --custom-favicon-files Dark=frontend/public/imgs/okd-favicon.png,Light=frontend/public/imgs/okd-favicon.png

openshift-ci-robot · 2025-02-10T17:20:39Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-10T17:22:15Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-10T17:22:30Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-10T17:22:45Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-10T17:23:07Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-10T17:23:40Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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.

Mylanos · 2025-02-11T11:01:25Z

cmd/bridge/main.go

@@ -110,6 +110,8 @@ func main() {

 	fBranding := fs.String("branding", "okd", "Console branding for the masthead logo and title. One of okd, openshift, ocp, online, dedicated, azure, or rosa. Defaults to okd.")
 	fCustomProductName := fs.String("custom-product-name", "", "Custom product name for console branding.")
+
+	fCustomLogoFiles := fs.String("custom-logo-files", "", "List of custom product images for console branding. Each entry consist of theme type as a key and path as a value.")


update the info string

openshift-ci-robot · 2025-02-11T11:03:03Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-11T11:49:23Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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.

Mylanos · 2025-02-11T15:52:50Z

pkg/serverconfig/custom_logos.go

+		serverutils.SendResponse(w, http.StatusBadRequest, serverutils.ApiError{Err: errMsg})
+		return
+	}
+	// logo is a public content and revalidate the each new request before releasing cached files


Suggested change

// logo is a public content and revalidate the each new request before releasing cached files

// logo is a public content, revalidate each new request before releasing cached files

openshift-ci-robot · 2025-02-14T11:53:13Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-14T15:49:21Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-14T15:49:25Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-14T15:49:39Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-14T15:49:49Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-17T13:40:06Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-17T13:40:38Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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-robot · 2025-02-17T16:24:11Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

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.

frontend/public/components/about-modal.tsx

cmd/bridge/main.go

rhamilto · 2025-04-15T20:49:18Z

Well that didn't work. 🤔

rhamilto · 2025-04-15T20:49:48Z

Right as I posted that it refreshed. 🥇

Mylanos · 2025-04-15T21:11:01Z

Found one bug in backend and one go.mod issue
will update asap

yapei · 2025-04-17T06:24:50Z

cmd/bridge/main.go

-	fCustomLogoFile := fs.String("custom-logo-file", "", "Custom product image for console branding.")
+
+	customLogoFlags := serverconfig.LogosKeyValue{}
+	fs.Var(&customLogoFlags, "custom-logo-files", "List of custom product images used for console branding. Each entry consist of theme type (Dark | Light | Default) as a key and path to image file as value.")


spec.customization.customLogoFile field is still valid for consoles.operator configuration although only one of spec.customization.customLogoFile and spec.customization.logos can take effect, shall we keep flag -custom-logo-file ?

As far as I understand, even though spec.customization.customLogoFile is marked as deprecated console.operator had to keep the configuration for backwards compatibility, so we won't affect customers still having the customLogoFile OpenShift API configured. In reality what CO does in case there is a customLogoFile OpenShift configuration still present is that it just feeds it to the new Logos API to configure the Masthead type custom logo for all themes ( light and dark currently). So in the end console.operator will always pass the customLogo configuration to bridge/console via the new Logos API inside the console-config.

I think we have decided to remove this configuration from bridge, due to its nature of being only a secondary API to console.operator, meaning this configuration is meant for developers of the bridge/console only and no real customer should be dependent on this.

cc @jhadvig @TheRealJon to confirm or deny.

Make sense, thank you @Mylanos

yapei · 2025-04-17T06:32:05Z

cmd/bridge/main.go

+	customLogoFlags := serverconfig.LogosKeyValue{}
+	fs.Var(&customLogoFlags, "custom-logo-files", "List of custom product images used for console branding. Each entry consist of theme type (Dark | Light | Default) as a key and path to image file as value.")
+	customFaviconFlags := serverconfig.LogosKeyValue{}
+	fs.Var(&customFaviconFlags, "custom-favicon-files", "List of custom product images used for console branding. Each entry consist of theme type (Dark | Light | Default) as a key and path to image file as value.")


Shall we update the help message for -custom-favicon-files flag? It's exactly the same as -custom-logo-files

Good catch, will update.

yapei · 2025-04-17T06:41:19Z

In my testing, I don't see favicon is updated when switching between Light and Dark theme via web console(switching via browser works), see recording

favicon-remains-same.mov

and here is my configuration

$ oc create configmap custom-logo-dark-name --from-file=/Users/yapei/Desktop/custom-logo-dark.svg -n openshift-config
configmap/custom-logo-dark-name created
$ oc create configmap custom-logo-light-name --from-file=/Users/yapei/Desktop/custom-logo-light.svg -n openshift-config
configmap/custom-logo-light-name created
$ oc create configmap custom-favicon-light-name --from-file=/Users/yapei/Desktop/custom-favicon-light.svg -n openshift-config
configmap/custom-favicon-light-name created
$ oc create configmap custom-favicon-dark-name --from-file=/Users/yapei/Desktop/custom-favicon-dark.svg -n openshift-config
configmap/custom-favicon-dark-name created
$ oc get console.operator cluster -o json | jq .spec.customization.logos
[
  {
    "themes": [
      {
        "mode": "Light",
        "source": {
          "configMap": {
            "key": "custom-logo-light.svg",
            "name": "custom-logo-light-name"
          },
          "from": "ConfigMap"
        }
      },
      {
        "mode": "Dark",
        "source": {
          "configMap": {
            "key": "custom-logo-dark.svg",
            "name": "custom-logo-dark-name"
          },
          "from": "ConfigMap"
        }
      }
    ],
    "type": "Masthead"
  },
  {
    "themes": [
      {
        "mode": "Light",
        "source": {
          "configMap": {
            "key": "custom-favicon-light.svg",
            "name": "custom-favicon-light-name"
          },
          "from": "ConfigMap"
        }
      },
      {
        "mode": "Dark",
        "source": {
          "configMap": {
            "key": "custom-favicon-dark.svg",
            "name": "custom-favicon-dark-name"
          },
          "from": "ConfigMap"
        }
      }
    ],
    "type": "Favicon"
  }
]

yanpzhan · 2025-04-17T07:47:50Z

Another issue: any time user refreshs console page, it will show default masthead logo and favicon for a while, then custom masthead logo and favicon shows up. It's better not show default logo.
AwesomeScreenshot-4_17_2025,3_40_44PM.webm

rhamilto · 2025-04-17T13:31:24Z

This is expected. The favicon should only change when the system preference is changed. Why? That's what results in the browser's tab color changing. Note there is a known limitation because of this behavioral difference: if the user preference is set to Light or Dark and the user changes the system preference, the favicon will not change until the browser is refreshed (you'll note it does change if the user preference is System default).

rhamilto · 2025-04-17T13:34:09Z

This should only happen if custom product name is not set, which should be less common since we instruct users to set both.

…ue Set

…tion if there is a favicon or customLogo customization

…ic logos when custom logos have not been fetched yet. Used the newly introduced SERVER_FLAGS customFaviconsConfigured and customLogosConfigured in a logic that prevents attempts to fetch custom logo type that is not configured.

openshift-ci · 2025-04-18T01:08:02Z

@Mylanos: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/okd-scos-e2e-aws-ovn	`940f17d`	link	false	`/test okd-scos-e2e-aws-ovn`
ci/prow/analyze	`940f17d`	link	true	`/test analyze`
ci/prow/frontend	`940f17d`	link	true	`/test frontend`
ci/prow/e2e-gcp-console	`940f17d`	link	true	`/test e2e-gcp-console`
ci/prow/backend	`940f17d`	link	true	`/test backend`

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.

TheRealJon · 2025-04-18T19:10:40Z

@Mylanos @rhamilto There seems to be an issue rendering svg masthead logos. When I use svg files, the logo is rendered at 0 height and width. Maybe an issue with one of the PF components?

rhamilto · 2025-04-18T19:13:45Z

Do the SVGs have width and height attributes defined (e.g., https://github.com/openshift/console/blob/main/frontend/public/imgs/openshift-logo.svg?short_path=340083c#L1)? I'm guessing they don't.

rhamilto · 2025-04-18T19:16:14Z

If you use the same logos on the PatternFly web site, do they show up?

yanpzhan · 2025-04-21T07:57:04Z

@Mylanos @rhamilto The issue was that I saw empty masthead log when I only set custom masthead logo for one theme(light or dark). Eg, when I set custom masthead logo for dark theme, I could see the new masthead logo in dark theme, at the meanwhile I will see empty masthead log in light theme.

# oc get consoles.operator.openshift.io cluster -o json | jq '.spec.customization.logos'
[
  {
    "themes": [
      {
        "mode": "Dark",
        "source": {
          "configMap": {
            "key": "masthead-dark-logo.png",
            "name": "custom-logos-masthead-dark"
          },
          "from": "ConfigMap"
        }
      }
    ],
    "type": "Masthead"
  }
]

AwesomeScreenshot-4_21_2025.3_54_20PM.webm

TheRealJon · 2025-04-21T15:00:57Z

@yanpzhan Do you mind if we move forward with merging this and openshift/console-operator#963 and open a bug to address the above issue?

rhamilto · 2025-04-21T15:10:16Z

IMO, this is expected behavior. I do not think we should make assumptions about a user's intent. It'll make troubleshooting much easier.

TheRealJon · 2025-04-21T17:42:01Z

They didn't have height or width attributes. Went back and reproduced with the original customLogoFile API, and the same thing happens. Disregard.

yanpzhan · 2025-04-22T01:01:14Z

There is not blocking issue for current feature, we can discuss any confusion later, so approve the pr now.
/label qe-approved

openshift-ci-robot · 2025-04-22T01:01:20Z

@Mylanos: This pull request references CONSOLE-4404 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

This pull request references CONSOLE-4062 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

After:

Screen.Recording.2025-02-10.at.18.06.06.mov

bridge command used for testing:

./bin/bridge --custom-logo-files Dark=frontend/public/imgs/okd-logo-dark.svg,Light=frontend/public/imgs/okd-logo-light.svg --custom-favicon-files Dark=frontend/public/imgs/okd-favicon.png,Light=frontend/public/imgs/okd-favicon.png

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.

Mylanos · 2025-04-22T06:16:54Z

/retest

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 10, 2025

openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 10, 2025

openshift-ci bot requested review from jhadvig and TheRealJon February 10, 2025 17:21

openshift-ci bot added component/backend Related to backend component/core Related to console core functionality labels Feb 10, 2025

Mylanos commented Feb 11, 2025

View reviewed changes

Mylanos changed the title ~~[WIP]CONSOLE-4404: Add the ability to specify second logo [CONSOLE SIDE]~~ [WIP]CONSOLE-4404: Add the ability to specify second logo Feb 11, 2025

Mylanos commented Feb 11, 2025

View reviewed changes

Mylanos force-pushed the CONSOLE-4404-add-ability-for-second-logo-in-PF6 branch from d88af9e to b13008b Compare February 17, 2025 16:23

Mylanos commented Feb 18, 2025

View reviewed changes

frontend/public/components/about-modal.tsx Outdated Show resolved Hide resolved

Mylanos mentioned this pull request Feb 20, 2025

[WIP] CONSOLE-4062: add custom favicon #14770

Closed

Mylanos force-pushed the CONSOLE-4404-add-ability-for-second-logo-in-PF6 branch from b13008b to d65b514 Compare February 28, 2025 11:37

Mylanos commented Feb 28, 2025

View reviewed changes

cmd/bridge/main.go Outdated Show resolved Hide resolved

fix failing tests

2a5c1d9

Mylanos force-pushed the CONSOLE-4404-add-ability-for-second-logo-in-PF6 branch from 3e78d08 to 2a5c1d9 Compare April 15, 2025 21:16

yapei reviewed Apr 17, 2025

View reviewed changes

Mylanos added 4 commits April 17, 2025 18:44

update customLogos and customFavicons description

74f34e4

make logic for the LogosKeyValue Set method correspond to MultiKeyVal…

2527418

…ue Set

introduce new SERVER_FLAGS that provide console frontend with informa…

ce23313

…tion if there is a favicon or customLogo customization

Mylanos changed the title ~~[WIP]CONSOLE-4404,CONSOLE-4062: Add the ability to specify second logo, favicons~~ CONSOLE-4404,CONSOLE-4062: Add the ability to specify second logo, favicons Apr 17, 2025

openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 17, 2025

TheRealJon mentioned this pull request Apr 18, 2025

CONSOLE-4479,CONSOLE-4061: Update console operator to support new custom logos API openshift/console-operator#963

Open

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Apr 22, 2025

	// logo is a public content and revalidate the each new request before releasing cached files
	// logo is a public content, revalidate each new request before releasing cached files

CONSOLE-4404,CONSOLE-4062: Add the ability to specify second logo, favicons #14749

Are you sure you want to change the base?

CONSOLE-4404,CONSOLE-4062: Add the ability to specify second logo, favicons #14749

Conversation

Mylanos commented Feb 10, 2025 • edited Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 10, 2025 • edited by openshift-ci bot Loading

Mylanos Feb 11, 2025

Choose a reason for hiding this comment

openshift-ci-robot commented Feb 11, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 11, 2025 • edited by openshift-ci bot Loading

Mylanos Feb 11, 2025

Choose a reason for hiding this comment

openshift-ci-robot commented Feb 14, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 14, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 14, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 14, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 14, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 17, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 17, 2025 • edited by openshift-ci bot Loading

openshift-ci-robot commented Feb 17, 2025 • edited by openshift-ci bot Loading

rhamilto commented Apr 15, 2025

rhamilto commented Apr 15, 2025

Mylanos commented Apr 15, 2025

yapei Apr 17, 2025 • edited Loading

Choose a reason for hiding this comment

Mylanos Apr 17, 2025 • edited Loading

Choose a reason for hiding this comment

yapei Apr 18, 2025

Choose a reason for hiding this comment

yapei Apr 17, 2025

Choose a reason for hiding this comment

Mylanos Apr 17, 2025

Choose a reason for hiding this comment

yapei commented Apr 17, 2025 • edited Loading

yanpzhan commented Apr 17, 2025

rhamilto commented Apr 17, 2025

rhamilto commented Apr 17, 2025

openshift-ci bot commented Apr 18, 2025

TheRealJon commented Apr 18, 2025

rhamilto commented Apr 18, 2025

rhamilto commented Apr 18, 2025

yanpzhan commented Apr 21, 2025

TheRealJon commented Apr 21, 2025

rhamilto commented Apr 21, 2025

TheRealJon commented Apr 21, 2025

yanpzhan commented Apr 22, 2025

openshift-ci-robot commented Apr 22, 2025 • edited by openshift-ci bot Loading

Mylanos commented Apr 22, 2025

Mylanos commented Feb 10, 2025 •

edited

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 10, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 11, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 11, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 14, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 14, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 14, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 14, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 14, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 17, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 17, 2025 •

edited by openshift-ci bot

Loading

openshift-ci-robot commented Feb 17, 2025 •

edited by openshift-ci bot

Loading

yapei Apr 17, 2025 •

edited

Loading

Mylanos Apr 17, 2025 •

edited

Loading

yapei commented Apr 17, 2025 •

edited

Loading

openshift-ci-robot commented Apr 22, 2025 •

edited by openshift-ci bot

Loading