OCPBUGS-114669: Enable GCP custom universe domain support for CCO by rochacbruno · Pull Request #1083 · openshift/cloud-credential-operator

rochacbruno · 2026-08-27T14:43:05Z

Backport of #1068 to release-4.22.

Cherry-picks the GCP client and service-account changes that add support for custom (alternate) universe domains:

Set the universe domain on GCP API clients
Support domain-scoped service account email formatting
Replace the deprecated CredentialsFromJSON usage

It also bumps google.golang.org/api v0.252.0 -> v0.258.0, the minimal version providing option.WithAuthCredentialsJSON and option.CredentialsType used by the cherry-picked code. k8s.io/api stays at v0.35.2 and github.com/openshift/api is unchanged.

Note: the companion ccoctl change (#1073) is intentionally NOT included here. It depends on the GCPPlatformStatus.UniverseDomain field from openshift/api #2963 (CORS-4417), which has not yet been backported to openshift/api release-4.22.

Sets the universe domain when initializing GCP clients in order to support running in environments with non-default universe domains such as Google Cloud Dedicated, GCP's sovereign cloud offering. CCO will always use JSON-based creds, either service account with key or WIF. We must utilize the WithAuthCredentialsJSON function because it will use self-signed JWTs rather than oauth token exchange which fails in GCD. The authentication falls back to WithCredentials, as ccoctl can authenticate via the metadata server (obtaining credentials from the service account attached to a VM). (cherry picked from commit 8155da6)

In some cases, such as Google Dedicated Cloud, service accounts take on a different format. When the project has the format eu0:PROJECT_ID, the service account has the format: serviceAccount:SERVICE_ACCOUNT_NAME@PROJECT_ID.eu0.iam.gserviceaccount.com This commit adds some simnple handling for this case. (cherry picked from commit c284a20)

Updates from CredentialsFromJSON -> CredentialsFromJSONWithType to avoid using the deprecated function. This change is a no-op, only intended to avoid deprecation warnings. The new function takes a credential type parameter, which can be used to limit accepted credentials types, which is useful for validating credentials provided by external third parties. For OpenShift, cluster credentials are coming from first party users running clusters in their project, so we do not need to limit which credentials are accepted; therefore we just pass the type through from the credential to the function. (cherry picked from commit aeb83ab)

openshift-merge-bot · 2026-08-27T14:43:08Z

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

coderabbitai · 2026-08-27T14:43:13Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6dc0f121-ce50-4749-9bbd-c4d336771438

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

_{Comment @coderabbitai help to get the list of available commands.}

rochacbruno · 2026-08-27T14:43:16Z

/jira cherrypick OCPBUGS-112145

openshift-ci-robot · 2026-08-27T14:44:26Z

@rochacbruno: Jira Issue OCPBUGS-112145 has been cloned as Jira Issue OCPBUGS-114669. Will retitle bug to link to clone.
/retitle OCPBUGS-114669: Enable GCP custom universe domain support for CCO

Details

In response to this:

/jira cherrypick OCPBUGS-112145

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 · 2026-08-27T14:44:44Z

@rochacbruno: This pull request references Jira Issue OCPBUGS-114669, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-112145 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
expected dependent Jira Issue OCPBUGS-112145 to target a version in 5.0.0, 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.

Details

In response to this:

Backport of #1068 to release-4.22.

Cherry-picks the GCP client and service-account changes that add support for custom (alternate) universe domains:

Set the universe domain on GCP API clients

Support domain-scoped service account email formatting

Replace the deprecated CredentialsFromJSON usage

It also bumps google.golang.org/api v0.252.0 -> v0.258.0, the minimal version providing option.WithAuthCredentialsJSON and option.CredentialsType used by the cherry-picked code. k8s.io/api stays at v0.35.2 and github.com/openshift/api is unchanged.

Note: the companion ccoctl change (#1073) is intentionally NOT included here. It depends on the GCPPlatformStatus.UniverseDomain field from openshift/api #2963 (CORS-4417), which has not yet been backported to openshift/api release-4.22.

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.

rochacbruno · 2026-08-27T14:48:02Z

/jira refresh

openshift-ci-robot · 2026-08-27T14:48:10Z

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

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-112145 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-112145 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

Details

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.

codecov · 2026-08-27T14:58:13Z

Codecov Report

❌ Patch coverage is 17.02128% with 39 lines in your changes missing coverage. Please review.
✅ Project coverage is 46.80%. Comparing base (c69fe7e) to head (5c5bdc1).
⚠️ Report is 6 commits behind head on release-4.22.

Files with missing lines	Patch %	Lines
pkg/gcp/client.go	0.00%	30 Missing ⚠️
pkg/gcp/mock/client_generated.go	37.50%	5 Missing ⚠️
pkg/cmd/provisioning/gcp/credentials.go	0.00%	4 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff                @@
##           release-4.22    #1083      +/-   ##
================================================
- Coverage         46.88%   46.80%   -0.09%     
================================================
  Files                98       98              
  Lines             12558    12594      +36     
================================================
+ Hits               5888     5894       +6     
- Misses             6015     6045      +30     
  Partials            655      655

Files with missing lines	Coverage Δ
pkg/gcp/actuator/serviceaccount.go	`84.93% <100.00%> (+0.64%)`	⬆️
pkg/cmd/provisioning/gcp/credentials.go	`0.00% <0.00%> (ø)`
pkg/gcp/mock/client_generated.go	`83.18% <37.50%> (-1.11%)`	⬇️
pkg/gcp/client.go	`0.00% <0.00%> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

tthvo · 2026-08-27T19:40:36Z

/test security verify-deps

tthvo · 2026-08-27T20:13:25Z

@@ -1,4 +1,4 @@
-FROM golang:1.21 AS builder
+FROM golang:1.26 AS builder


Suggested change

FROM golang:1.26 AS builder

FROM golang:1.25 AS builder

I wonder if we can use go v1.25 instead here since 4.22 release is built with go v1.25? My guess is "yes" based on: https://github.com/googleapis/google-api-go-client/blob/182ae992632d7ba19b5d3c60c71bda28fbfabca1/go.mod#L3

Good catch, applied. Switched Dockerfile.local to golang:1.25 since release-4.22 is a Go 1.25 release (the go.mod go directive is 1.25.0, and google.golang.org/api v0.258.0 only requires Go 1.25). The golang:1.26 came from the #1068 cherry-pick, which targets master/5.0.

@tthvo I will have to bump to a new golang api version, 0.258.0 has a bug that was fixed on 0.288

Ah, right, thanks for checking that 🙏 The version v0.258.0 was indeed retracted (see here) due to that bug you described below :D

rochacbruno · 2026-08-31T11:54:04Z

On the failing ci/prow/security (Snyk) check: the 22 findings are all pre-existing on release-4.22 and are not introduced by this PR.

This PR only changes google.golang.org/api (0.252.0 -> 0.258.0), enterprise-certificate-proxy (0.3.6 -> 0.3.7), genproto/rpc (date bump), and protobuf (1.36.10 -> 1.36.11). None of these appear in Snyk's findings.
Every flagged package is at the identical version on the release-4.22 baseline (e.g. grpc v1.79.3, otel v1.40.0, golang.org/x/net v0.49.0 which is pinned via a replace directive, aws-sdk s3 v1.96.0), plus a set of Go stdlib CVEs tied to the CI toolchain (Go 1.25.12, fixed in 1.25.13). A fresh Snyk scan of release-4.22 HEAD would report the same issues; earlier PRs show green only because Snyk uses a live vulnerability DB and these CVEs were published more recently.

Addressing these belongs in a separate, repo-wide dependency bump rather than this targeted backport.

rochacbruno · 2026-08-31T16:54:35Z

/jira refresh

openshift-ci-robot · 2026-08-31T16:54:39Z

@rochacbruno: This pull request references Jira Issue OCPBUGS-114669, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-112145 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-112145 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

Details

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.

tthvo

/lgtm

openshift-merge-bot · 2026-08-31T17:23:26Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-cco-parallel
/test e2e-gcp-manual-oidc
/test e2e-aws-ovn
/test e2e-hypershift
/test e2e-upgrade

tthvo · 2026-08-31T17:29:26Z

/payload-job periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

openshift-ci · 2026-08-31T17:29:53Z

@tthvo: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/84b214b0-a561-11f1-9215-1a8b4a28958c-0

Fixes the e2e-gcp-manual-oidc failure "dialing: multiple credential options provided" seen when ccoctl builds a GCP client from credentials loaded via the gcloud CLI default path. In v0.258.0, DialSettings.Validate() counted both AuthCredentials and AuthCredentialsJSON toward the credential-option total. When option.WithAuthCredentialsJSON is auto-converted to an auth.Credentials for the new-auth gRPC/storage clients, both were set and validation rejected the dial as having multiple credential options. v0.288.0 no longer counts AuthCredentials in that total, treating it as a special case for oauth2 -> cloud.google.com/go/auth conversion. This matches the google.golang.org/api version already on master, where the identical NewClient code passes e2e-gcp-manual-oidc. k8s.io/api stays pinned at v0.35.2 and github.com/openshift/api is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

rochacbruno · 2026-08-31T21:18:08Z

The e2e-gcp-manual-oidc failure was ccoctl erroring with:

Failed to initiate GCP client: dialing: multiple credential options provided

Root cause is the google.golang.org/api version, not the cherry-picked CCO code. This branch had pulled in v0.258.0, whose DialSettings.Validate() counts both AuthCredentials and AuthCredentialsJSON toward the credential-option total. NewClient passes option.WithAuthCredentialsJSON(...), and for the new-auth gRPC/storage clients that JSON is auto-converted into an auth.Credentials, so both fields end up set and validation rejects the dial as having "multiple credential options".

v0.288.0 fixes this by no longer counting AuthCredentials in that total (it is treated as a special case for the oauth2 -> cloud.google.com/go/auth conversion). This is the same google.golang.org/api version already on master, where the identical NewClient code passes e2e-gcp-manual-oidc.

I bumped google.golang.org/api to v0.288.0 (k8s.io/api stays pinned at v0.35.2, github.com/openshift/api unchanged) and cleaned up the intermediate commits. Build is green locally.

tthvo

/lgtm

+1 for the failure analysis #1083 (comment) 🚀. This exact issue was filed and addressed in googleapis/google-cloud-go#13503.

openshift-merge-bot · 2026-08-31T22:05:15Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-cco-parallel
/test e2e-gcp-manual-oidc
/test e2e-aws-ovn
/test e2e-hypershift
/test e2e-upgrade

tthvo · 2026-08-31T22:05:18Z

/payload-job periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

openshift-ci · 2026-08-31T22:05:29Z

@tthvo: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

periodic-ci-openshift-release-main-ci-4.22-upgrade-from-stable-4.21-e2e-gcp-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0d89b560-a588-11f1-9064-e2968598da27-0

rochacbruno · 2026-09-01T08:16:09Z

The google.golang.org/api v0.288.0 bump fixed the credential error. In this run the cluster provisioned cleanly, ccoctl created the GCP resources without issue, and 2017 tests passed (the "multiple credential options provided" failure is gone).

The suite went red on two blocking failures that are unrelated to this backport and to CCO:

[sig-api-machinery] CRDValidationRatcheting ... MUST fail to update a resource due to JSONSchema errors on unchanged uncorrelatable fields
[sig-node] [DRA] kubelet [Feature:DynamicResourceAllocation] on single node retries pod scheduling after creating device class

Both are generic Kubernetes/OpenShift platform conformance tests. The only CCO-related failure (CCO metrics endpoint validation, PolarionID 88196) is an informing/non-blocking test and is unrelated to the universe-domain change, which only affects ccoctl GCP client construction, not the operator's metrics endpoint.

Re-running the job to clear the flakes.

/test e2e-gcp-manual-oidc

patrickdillon · 2026-09-01T20:06:53Z

/approve
/verified by testwith and e2es

openshift-ci-robot · 2026-09-01T20:07:06Z

@patrickdillon: This PR has been marked as verified by testwith and e2es.

Details

In response to this:

/approve
/verified by testwith and e2es

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.

rochacbruno · 2026-09-02T10:28:58Z

/cc @jstuever

dlom · 2026-09-02T17:44:16Z

/approve

dlom · 2026-09-02T17:44:26Z

/label backport-risk-assessed

openshift-ci · 2026-09-02T17:47:13Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dlom, patrickdillon, rochacbruno, tthvo

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [dlom]

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

openshift-merge-bot · 2026-09-02T18:08:36Z

/retest-required

Remaining retests: 0 against base HEAD c69fe7e and 2 for PR HEAD 5c5bdc1 in total

patrickdillon · 2026-09-02T23:16:53Z

/override ci/prow/security

openshift-ci · 2026-09-02T23:17:11Z

@patrickdillon: patrickdillon unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-ci-job-overriders openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override ci/prow/security

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.

dlom · 2026-09-03T19:02:53Z

/override ci/prow/security

openshift-ci · 2026-09-03T19:04:06Z

@dlom: Overrode contexts on behalf of dlom: ci/prow/security

Details

In response to this:

/override ci/prow/security

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.

openshift-ci · 2026-09-03T19:04:11Z

@rochacbruno: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 · 2026-09-03T19:10:25Z

@rochacbruno: Jira Issue Verification Checks: Jira Issue OCPBUGS-114669
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-114669 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Backport of #1068 to release-4.22.

Cherry-picks the GCP client and service-account changes that add support for custom (alternate) universe domains:

Set the universe domain on GCP API clients

Support domain-scoped service account email formatting

Replace the deprecated CredentialsFromJSON usage

It also bumps google.golang.org/api v0.252.0 -> v0.258.0, the minimal version providing option.WithAuthCredentialsJSON and option.CredentialsType used by the cherry-picked code. k8s.io/api stays at v0.35.2 and github.com/openshift/api is unchanged.

Note: the companion ccoctl change (#1073) is intentionally NOT included here. It depends on the GCPPlatformStatus.UniverseDomain field from openshift/api #2963 (CORS-4417), which has not yet been backported to openshift/api release-4.22.

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.

patrickdillon added 3 commits August 27, 2026 14:43

openshift-ci Bot changed the title ~~Enable GCP custom universe domain support for CCO~~ OCPBUGS-114669: Enable GCP custom universe domain support for CCO Aug 27, 2026

openshift-ci-robot added 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 Aug 27, 2026

openshift-ci Bot requested review from 2uasimojo and dlom August 27, 2026 14:45

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 Aug 27, 2026

tthvo reviewed Aug 27, 2026

View reviewed changes

patrickdillon mentioned this pull request Aug 29, 2026

OCPBUGS-114639: OCPBUGS-112550, OCPBUGS-112549: Release 4.22 GCD and KMS support openshift/installer#10783

Merged

tthvo reviewed Aug 31, 2026

View reviewed changes

openshift-ci Bot assigned tthvo Aug 31, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2026

rochacbruno force-pushed the backport-1068-release-4.22 branch from cdf09a9 to 5c5bdc1 Compare August 31, 2026 21:17

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2026

tthvo reviewed Aug 31, 2026

View reviewed changes

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 1, 2026

openshift-ci Bot requested a review from jstuever September 2, 2026 10:29

2uasimojo removed their request for review September 2, 2026 15:51

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 2, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2026

patrickdillon mentioned this pull request Sep 2, 2026

OCPBUGS-119240: gcp: allow GCD load balancer health-check firewall ranges openshift/installer#10853

Open

openshift-merge-bot Bot merged commit 26005d2 into openshift:release-4.22 Sep 3, 2026
14 checks passed

		@@ -1,4 +1,4 @@
		FROM golang:1.21 AS builder
		FROM golang:1.26 AS builder

Uh oh!

Conversation

rochacbruno commented Aug 27, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-merge-bot Bot commented Aug 27, 2026

Uh oh!

coderabbitai Bot commented Aug 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

rochacbruno commented Aug 27, 2026

Uh oh!

openshift-ci-robot commented Aug 27, 2026

Uh oh!

openshift-ci-robot commented Aug 27, 2026

Uh oh!

rochacbruno commented Aug 27, 2026

Uh oh!

openshift-ci-robot commented Aug 27, 2026

Uh oh!

codecov Bot commented Aug 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

tthvo commented Aug 27, 2026

Uh oh!

tthvo Aug 27, 2026

Choose a reason for hiding this comment

Uh oh!

rochacbruno Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

rochacbruno Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

tthvo Aug 31, 2026

Choose a reason for hiding this comment

Uh oh!

rochacbruno commented Aug 31, 2026

Uh oh!

rochacbruno commented Aug 31, 2026

Uh oh!

openshift-ci-robot commented Aug 31, 2026

Uh oh!

tthvo left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-merge-bot Bot commented Aug 31, 2026

Uh oh!

tthvo commented Aug 31, 2026

Uh oh!

openshift-ci Bot commented Aug 31, 2026

Uh oh!

rochacbruno commented Aug 31, 2026

Uh oh!

tthvo left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-merge-bot Bot commented Aug 31, 2026

Uh oh!

tthvo commented Aug 31, 2026

Uh oh!

openshift-ci Bot commented Aug 31, 2026

Uh oh!

rochacbruno commented Sep 1, 2026

Uh oh!

patrickdillon commented Sep 1, 2026

Uh oh!

openshift-ci-robot commented Sep 1, 2026

Uh oh!

rochacbruno commented Sep 2, 2026

Uh oh!

dlom commented Sep 2, 2026

Uh oh!

dlom commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 2, 2026

rochacbruno commented Aug 27, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Aug 27, 2026 •

edited

Loading

codecov Bot commented Aug 27, 2026 •

edited

Loading