[release-4.21] OCPBUGS-104592: Add proxy env vars to AWS cloud-controller-manager deployment by openshift-cherrypick-robot · Pull Request #9224 · openshift/hypershift

openshift-cherrypick-robot · 2026-08-05T09:51:39Z

This is an automated cherry-pick of #9156

/assign openshift-ci-robot

…r deployment The CCM deployment was missing HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables when the management cluster is configured with a proxy. This was a regression from the v1 to v2 component framework migration where the proxy.SetEnvVars() call was not carried over. Adapted for release-4.22: uses support/util instead of support/podspec (which doesn't exist on this branch). Adds the missing FindEnvVar helper to support/util/containers.go. Includes test coverage for full proxy, partial proxy (HTTP_PROXY-only and HTTPS_PROXY-only), no proxy, and env var preservation scenarios. This is a manual backport of PR openshift#9053 (commits ec5ae7a, 4afcef2) adapted for the release-4.22 branch.

openshift-merge-bot · 2026-08-05T09:51:41Z

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

openshift-ci-robot · 2026-08-05T09:51:43Z

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-100141 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.21] OCPBUGS-104592: Add proxy env vars to AWS cloud-controller-manager deployment

Details

In response to this:

This is an automated cherry-pick of #9156

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

coderabbitai · 2026-08-05T09:51:48Z

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: dae28627-f49a-475e-afa5-1dafee6da81f

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-05T09:52:00Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-104592, which is invalid:

expected dependent Jira Issue OCPBUGS-100141 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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 #9156

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

PoornimaSingour · 2026-08-06T14:58:49Z

/jira refresh

openshift-ci-robot · 2026-08-06T14:58:57Z

@PoornimaSingour: This pull request references Jira Issue OCPBUGS-104592, 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.21.z) matches configured target version for branch (4.21.z)
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-100141 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-100141 targets the "4.22.0" version, which is one of the valid target versions: 4.22.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.

muraee · 2026-08-07T13:25:02Z

/approve

openshift-ci · 2026-08-07T13:25:36Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: muraee, 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~~ [muraee]

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

bryan-cox · 2026-08-07T15:05:44Z

/lgtm

openshift-merge-bot · 2026-08-07T15:06:26Z

Scheduling required tests:
/test verify-deps

vsolanki12 · 2026-08-11T12:19:42Z

/verified by @vsolanki12

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

All 4 test cases pass:

  $ go test -v -run TestAdaptDeployment ./control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws/
  === RUN   TestAdaptDeployment
  === RUN   TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container
  === RUN   TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY
  === RUN   TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY
  === RUN   TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars
  --- PASS: TestAdaptDeployment (0.00s)
      --- PASS: TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container (0.00s)
      --- PASS: TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY (0.00s)
      --- PASS: TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY (0.00s)
      --- PASS: TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars (0.00s)
  PASS
  ok    github.com/openshift/hypershift/control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws   1.339s

Live Cluster Testing

Environment:

Management cluster: OCP 4.22 (ap-south-1)
Hosted cluster: pr9224 (AWS, release-4.21.28-multi)
Custom CPO image: quay.io/vsolanki/hypershift:pr-9224-cpo-v3 (built from clean upstream/release-4.21 + cherry-picked PR commit 17180f54d3)

Path A — No proxy

CPO running without proxy env vars. CCM deployment has only AWS credential env vars:

[
    {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
    {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
    {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"}
]

Result: No HTTP_PROXY/HTTPS_PROXY/NO_PROXY injected — correct behavior when management cluster has no proxy.

Path B — Proxy injected

  Set proxy env vars on CPO deployment:
  HTTP_PROXY=http://test-proxy.example.com:3128
  HTTPS_PROXY=http://test-proxy.example.com:3128
  NO_PROXY=.cluster.local,.svc,10.128.0.0/14,172.30.0.0/16,localhost,.amazonaws.com,quay.io,.quay.io,registry.redhat.io,.redhat.io,.redhat.com

  After CPO reconciliation, CCM deployment env vars:
  [
      {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
      {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
      {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"},
      {"name": "HTTP_PROXY", "value": "http://test-proxy.example.com:3128"},
      {"name": "HTTPS_PROXY", "value": "http://test-proxy.example.com:3128"},
      {"name": "NO_PROXY", "value": ".amazonaws.com,.cluster.local,.quay.io,.redhat.com,.redhat.io,.svc,10.128.0.0/14,172.30.0.0/16,kube-apiserver,localhost,quay.io,registry.redhat.io"}
  ]

Result: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY correctly propagated to CCM container. NO_PROXY auto-appended kube-apiserver as expected by proxy.SetEnvVars().

openshift-ci-robot · 2026-08-11T12:19:55Z

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

Details

In response to this:

/verified by @vsolanki12

/verified

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

All 4 test cases pass:

 $ go test -v -run TestAdaptDeployment ./control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws/
 === RUN   TestAdaptDeployment
 === RUN   TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container
 === RUN   TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY
 === RUN   TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY
 === RUN   TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars
 --- PASS: TestAdaptDeployment (0.00s)
     --- PASS: TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container (0.00s)
     --- PASS: TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY (0.00s)
     --- PASS: TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY (0.00s)
     --- PASS: TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars (0.00s)
 PASS
 ok    github.com/openshift/hypershift/control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws   1.339s

Live Cluster Testing

Environment:

Management cluster: OCP 4.22 (ap-south-1)
Hosted cluster: pr9224 (AWS, release-4.21.28-multi)
Custom CPO image: quay.io/vsolanki/hypershift:pr-9224-cpo-v3 (built from clean upstream/release-4.21 + cherry-picked PR commit 17180f54d3)

Path A — No proxy

CPO running without proxy env vars. CCM deployment has only AWS credential env vars:

[
    {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
    {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
    {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"}
]

Result: No HTTP_PROXY/HTTPS_PROXY/NO_PROXY injected — correct behavior when management cluster has no proxy.

Path B — Proxy injected

 Set proxy env vars on CPO deployment:
 HTTP_PROXY=http://test-proxy.example.com:3128
 HTTPS_PROXY=http://test-proxy.example.com:3128
 NO_PROXY=.cluster.local,.svc,10.128.0.0/14,172.30.0.0/16,localhost,.amazonaws.com,quay.io,.quay.io,registry.redhat.io,.redhat.io,.redhat.com

 After CPO reconciliation, CCM deployment env vars:
 [
     {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
     {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
     {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"},
     {"name": "HTTP_PROXY", "value": "http://test-proxy.example.com:3128"},
     {"name": "HTTPS_PROXY", "value": "http://test-proxy.example.com:3128"},
     {"name": "NO_PROXY", "value": ".amazonaws.com,.cluster.local,.quay.io,.redhat.com,.redhat.io,.svc,10.128.0.0/14,172.30.0.0/16,kube-apiserver,localhost,quay.io,registry.redhat.io"}
 ]

Result: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY correctly propagated to CCM container. NO_PROXY auto-appended kube-apiserver as expected by proxy.SetEnvVars().

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-11T12:19:56Z

@vsolanki12: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified by @vsolanki12

/verified

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

All 4 test cases pass:

 $ go test -v -run TestAdaptDeployment ./control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws/
 === RUN   TestAdaptDeployment
 === RUN   TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container
 === RUN   TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY
 === RUN   TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY
 === RUN   TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars
 --- PASS: TestAdaptDeployment (0.00s)
     --- PASS: TestAdaptDeployment/When_proxy_environment_variables_are_set,_it_should_add_proxy_env_vars_to_container (0.00s)
     --- PASS: TestAdaptDeployment/When_only_HTTP_PROXY_is_set,_it_should_add_HTTP_PROXY_and_NO_PROXY_but_not_HTTPS_PROXY (0.00s)
     --- PASS: TestAdaptDeployment/When_only_HTTPS_PROXY_is_set,_it_should_add_HTTPS_PROXY_and_NO_PROXY_but_not_HTTP_PROXY (0.00s)
     --- PASS: TestAdaptDeployment/When_no_proxy_is_set,_it_should_not_add_proxy_env_vars (0.00s)
 PASS
 ok    github.com/openshift/hypershift/control-plane-operator/controllers/hostedcontrolplane/v2/cloud_controller_manager/aws   1.339s

Live Cluster Testing

Environment:

Management cluster: OCP 4.22 (ap-south-1)
Hosted cluster: pr9224 (AWS, release-4.21.28-multi)
Custom CPO image: quay.io/vsolanki/hypershift:pr-9224-cpo-v3 (built from clean upstream/release-4.21 + cherry-picked PR commit 17180f54d3)

Path A — No proxy

CPO running without proxy env vars. CCM deployment has only AWS credential env vars:

[
    {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
    {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
    {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"}
]

Result: No HTTP_PROXY/HTTPS_PROXY/NO_PROXY injected — correct behavior when management cluster has no proxy.

Path B — Proxy injected

 Set proxy env vars on CPO deployment:
 HTTP_PROXY=http://test-proxy.example.com:3128
 HTTPS_PROXY=http://test-proxy.example.com:3128
 NO_PROXY=.cluster.local,.svc,10.128.0.0/14,172.30.0.0/16,localhost,.amazonaws.com,quay.io,.quay.io,registry.redhat.io,.redhat.io,.redhat.com

 After CPO reconciliation, CCM deployment env vars:
 [
     {"name": "AWS_SHARED_CREDENTIALS_FILE", "value": "/etc/kubernetes/secrets/cloud-provider/credentials"},
     {"name": "AWS_SDK_LOAD_CONFIG", "value": "true"},
     {"name": "AWS_EC2_METADATA_DISABLED", "value": "true"},
     {"name": "HTTP_PROXY", "value": "http://test-proxy.example.com:3128"},
     {"name": "HTTPS_PROXY", "value": "http://test-proxy.example.com:3128"},
     {"name": "NO_PROXY", "value": ".amazonaws.com,.cluster.local,.quay.io,.redhat.com,.redhat.io,.svc,10.128.0.0/14,172.30.0.0/16,kube-apiserver,localhost,quay.io,registry.redhat.io"}
 ]

Result: HTTP_PROXY, HTTPS_PROXY, and NO_PROXY correctly propagated to CCM container. NO_PROXY auto-appended kube-apiserver as expected by proxy.SetEnvVars().

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 · 2026-08-11T20:48: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-11T20:52:10Z

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

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

PoornimaSingour · 2026-08-12T05:14:43Z

/jira backport release-4.20

openshift-ci-robot · 2026-08-12T05:15:54Z

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-105812 for branch release-4.20

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

Details

In response to this:

/jira backport release-4.20

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-08-12T05:16:44Z

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

Details

In response to this:

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-105812 for branch release-4.20

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

In response to this:

/jira backport release-4.20

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.

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

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

[release-4.22] OCPBUGS-100141: Add proxy env vars to AWS cloud-controller-manager deployment #9156

Merged

openshift-ci Bot changed the title ~~[release-4.21] OCPBUGS-100141: Add proxy env vars to AWS cloud-controller-manager deployment~~ [release-4.21] OCPBUGS-104592: Add proxy env vars to AWS cloud-controller-manager deployment Aug 5, 2026

openshift-ci Bot added the do-not-merge/needs-area label Aug 5, 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 5, 2026

openshift-ci Bot requested review from bryan-cox and enxebre August 5, 2026 09:54

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

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

openshift-ci Bot assigned bryan-cox Aug 7, 2026

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

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

csrwng added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 11, 2026

openshift-merge-bot Bot merged commit 4298ee0 into openshift:release-4.21 Aug 11, 2026
19 checks passed

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

[release-4.20] OCPBUGS-105812: Add proxy env vars to AWS cloud-controller-manager deployment #9284

Open

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 5, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 5, 2026

Uh oh!

openshift-ci-robot commented Aug 5, 2026

Uh oh!

coderabbitai Bot commented Aug 5, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Aug 5, 2026

Uh oh!

PoornimaSingour commented Aug 6, 2026

Uh oh!

openshift-ci-robot commented Aug 6, 2026

Uh oh!

muraee commented Aug 7, 2026

Uh oh!

openshift-ci Bot commented Aug 7, 2026

Uh oh!

bryan-cox commented Aug 7, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 7, 2026

Uh oh!

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

Uh oh!

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

Live Cluster Testing

Path A — No proxy

Path B — Proxy injected

Uh oh!

openshift-ci-robot commented Aug 11, 2026

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

Live Cluster Testing

Path A — No proxy

Path B — Proxy injected

Uh oh!

openshift-ci-robot commented Aug 11, 2026

Verification: PR #9224 — Add proxy env vars to AWS CCM (release-4.21 backport)

Unit Tests

Live Cluster Testing

Path A — No proxy

Path B — Proxy injected

Uh oh!

openshift-ci Bot commented Aug 11, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 11, 2026

Uh oh!

PoornimaSingour commented Aug 12, 2026

Uh oh!

openshift-ci-robot commented Aug 12, 2026

Uh oh!

openshift-cherrypick-robot commented Aug 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

vsolanki12 commented Aug 11, 2026 •

edited

Loading