[release-5.0] OCPBUGS-111893: Add proxy hook for HyperShift CSI driver controller deployments by openshift-cherrypick-robot · Pull Request #599 · openshift/csi-operator

openshift-cherrypick-robot · 2026-08-18T12:48:15Z

This is an automated cherry-pick of #594

/assign openshift-ci-robot

…ler deployments The HyperShift mode was missing a proxy hook in NewDefaultOperatorControllerConfig, leaving CSI driver controller containers without HTTP_PROXY, HTTPS_PROXY, and NO_PROXY when the management cluster requires a proxy for external access.

openshift-ci-robot · 2026-08-18T12:48:18Z

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-105392 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-5.0] OCPBUGS-111893: Add proxy hook for HyperShift CSI driver controller deployments

Details

In response to this:

This is an automated cherry-pick of #594

/assign openshift-ci-robot

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-merge-bot · 2026-08-18T12:48:19Z

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-18T12:48:26Z

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 YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: d34404c7-dba3-40de-8e4c-2d2899e0ac39

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

openshift-ci-robot · 2026-08-18T12:48:40Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-111893, 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-105392 to target a version in 5.1.0, but it targets "5.0" instead

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:

This is an automated cherry-pick of #594

/assign openshift-ci-robot

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.

jsafrane · 2026-08-18T15:13:56Z

/lgtm
/approve
/label backport-risk-assessed

openshift-merge-bot · 2026-08-18T15:15:52Z

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-azure-file-nfs-csi
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-csi
/test e2e-gcp-ovn-upgrade

openshift-ci · 2026-08-18T15:16:00Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, openshift-cherrypick-robot

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~~ [jsafrane]

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

jsafrane · 2026-08-18T15:17:03Z

/jira refresh

openshift-ci-robot · 2026-08-18T15:17:07Z

@jsafrane: This pull request references Jira Issue OCPBUGS-111893, 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-105392 to target a version in 5.1.0, but it targets "5.0" instead

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.

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.

jsafrane · 2026-08-18T15:18:10Z

/jira refresh

openshift-ci-robot · 2026-08-18T15:18:15Z

@jsafrane: This pull request references Jira Issue OCPBUGS-111893, 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.

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.

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.

jsafrane · 2026-08-18T15:18:55Z

/jira refresh

openshift-ci-robot · 2026-08-18T15:19:03Z

@jsafrane: This pull request references Jira Issue OCPBUGS-111893, 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 (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-105392 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-105392 targets the "5.1" version, which is one of the valid target versions: 5.1.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.

openshift-merge-bot · 2026-08-18T15:44:44Z

/retest-required

Remaining retests: 0 against base HEAD b967312 and 2 for PR HEAD fb99434 in total

PoornimaSingour · 2026-08-19T02:42:49Z

/retest

PoornimaSingour · 2026-08-19T16:41:40Z

/retest

vsolanki12 · 2026-08-20T06:49:23Z

/verified by @vsolanki

Test result:
Step 1: CPO sets proxy on CSO

    $ oc get deployment cluster-storage-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: cluster-storage-operator
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 2: CSO sets proxy on aws-ebs-csi-driver-operator

    $ oc get deployment aws-ebs-csi-driver-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: aws-ebs-csi-driver-operator
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost
    Container: token-minter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 3: aws-ebs-csi-driver-operator sets proxy on aws-ebs-csi-driver-controller (all 12 containers)

  $ oc get deployment aws-ebs-csi-driver-controller -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: csi-driver
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128

    Container: csi-provisioner
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-attacher
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-resizer
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-snapshotter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-liveness-probe
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: token-minter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    (+ 5 kube-rbac-proxy sidecar containers, all with same proxy vars)

  PVC Provisioning Test (end-to-end proof)
  Guest cluster nodes
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get nodes
    NAME                          STATUS   ROLES    AGE   VERSION
    ip-10-0-128-46.ec2.internal   Ready    worker   10m   v1.35.3
    ip-10-0-133-12.ec2.internal   Ready    worker   10m   v1.35.3

    PVC status — Bound
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pvc -n default
    NAME             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
    proxy-test-pvc   Bound    pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            gp3-csi        48m

  PV details — gp3 EBS volume provisioned
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pv
   NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM
   STORAGECLASS   AGE
   pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            Delete           Bound    default/proxy-test-pvc
   gp3-csi        8m56s

  Pod status — Running
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pod proxy-test-pod -n default
    NAME             READY   STATUS    RESTARTS   AGE
    proxy-test-pod   1/1     Running   0          48m

This proves aws-ebs-csi-driver-controller now reach AWS STS through proxy, assume IAM role, call EC2 CreateVolume ok.

openshift-ci-robot · 2026-08-20T06:49:34Z

@vsolanki12: This PR has been marked as verified by @vsolanki.

Details

In response to this:

/verified by @vsolanki

Test result:
Step 1: CPO sets proxy on CSO

   $ oc get deployment cluster-storage-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: cluster-storage-operator
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 2: CSO sets proxy on aws-ebs-csi-driver-operator

   $ oc get deployment aws-ebs-csi-driver-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: aws-ebs-csi-driver-operator
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost
   Container: token-minter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 3: aws-ebs-csi-driver-operator sets proxy on aws-ebs-csi-driver-controller (all 12 containers)

 $ oc get deployment aws-ebs-csi-driver-controller -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: csi-driver
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128

   Container: csi-provisioner
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-attacher
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-resizer
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-snapshotter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-liveness-probe
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: token-minter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   (+ 5 kube-rbac-proxy sidecar containers, all with same proxy vars)

 PVC Provisioning Test (end-to-end proof)
 Guest cluster nodes
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get nodes
   NAME                          STATUS   ROLES    AGE   VERSION
   ip-10-0-128-46.ec2.internal   Ready    worker   10m   v1.35.3
   ip-10-0-133-12.ec2.internal   Ready    worker   10m   v1.35.3

   PVC status — Bound
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pvc -n default
   NAME             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   proxy-test-pvc   Bound    pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            gp3-csi        48m

 PV details — gp3 EBS volume provisioned
  $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pv
  NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM
  STORAGECLASS   AGE
  pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            Delete           Bound    default/proxy-test-pvc
  gp3-csi        8m56s

 Pod status — Running
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pod proxy-test-pod -n default
   NAME             READY   STATUS    RESTARTS   AGE
   proxy-test-pod   1/1     Running   0          48m

This proves aws-ebs-csi-driver-controller now reach AWS STS through proxy, assume IAM role, call EC2 CreateVolume ok.

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.

PoornimaSingour · 2026-08-20T07:01:05Z

/retest

PoornimaSingour · 2026-08-20T10:40:02Z

/retest

PoornimaSingour · 2026-08-20T13:31:11Z

/retest

PoornimaSingour · 2026-08-20T14:20:48Z

/test e2e-azure

openshift-ci · 2026-08-20T17:43:19Z

@openshift-cherrypick-robot: 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-08-20T17:46:48Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-111893
✔️ 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-111893 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:

This is an automated cherry-pick of #594

/assign openshift-ci-robot

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-merge-robot · 2026-08-21T10:52:22Z

Fix included in release 5.0.0-0.nightly-2026-08-21-033959

PoornimaSingour · 2026-09-03T02:50:44Z

/jira backport release-4.22

openshift-ci-robot · 2026-09-03T02:51:54Z

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-119697 for branch release-4.22

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

Details

In response to this:

/jira backport 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.

openshift-cherrypick-robot · 2026-09-03T02:52:41Z

@openshift-ci-robot: new pull request created: #619

Details

In response to this:

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-119697 for branch release-4.22

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

In response to this:

/jira backport 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.

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.

PoornimaSingour added 2 commits August 18, 2026 12:48

OCPBUGS-105392: clear ambient proxy env vars in test setup

fb99434

openshift-cherrypick-robot assigned openshift-ci-robot Aug 18, 2026

openshift-cherrypick-robot mentioned this pull request Aug 18, 2026

OCPBUGS-105392: Add proxy hook for HyperShift CSI driver controller deployments #594

Merged

4 tasks

openshift-ci Bot changed the title ~~[release-5.0] OCPBUGS-105392: Add proxy hook for HyperShift CSI driver controller deployments~~ [release-5.0] OCPBUGS-111893: Add proxy hook for HyperShift CSI driver controller deployments Aug 18, 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 18, 2026

openshift-ci Bot requested review from gnufied and jsafrane August 18, 2026 12: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 Aug 18, 2026

openshift-ci Bot assigned radeore and jsafrane Aug 18, 2026

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

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

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 18, 2026

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

openshift-merge-bot Bot merged commit 8093776 into openshift:release-5.0 Aug 20, 2026
24 checks passed

openshift-cherrypick-robot mentioned this pull request Sep 3, 2026

[release-4.22] OCPBUGS-119697: Add proxy hook for HyperShift CSI driver controller deployments #619

Open

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 18, 2026

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 18, 2026

Uh oh!

coderabbitai Bot commented Aug 18, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

jsafrane commented Aug 18, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 18, 2026

Uh oh!

openshift-ci Bot commented Aug 18, 2026

Uh oh!

jsafrane commented Aug 18, 2026

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

jsafrane commented Aug 18, 2026

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

jsafrane commented Aug 18, 2026

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 18, 2026

Uh oh!

PoornimaSingour commented Aug 19, 2026

Uh oh!

PoornimaSingour commented Aug 19, 2026

Uh oh!

vsolanki12 commented Aug 20, 2026

Uh oh!

openshift-ci-robot commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

openshift-ci Bot commented Aug 20, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 20, 2026

Uh oh!

openshift-merge-robot commented Aug 21, 2026

Uh oh!

PoornimaSingour commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

openshift-cherrypick-robot commented Sep 3, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants