[release-4.20] OCPBUGS-99476: Respect proxy configuration on gwapi provisioning by openshift-cherrypick-robot · Pull Request #1519 · openshift/cluster-ingress-operator

openshift-cherrypick-robot · 2026-07-22T16:40:32Z

This is an automated cherry-pick of #1383

/assign rikatz

This PR adds support for global proxy configuration on Gateway API provisioning. It mutates the Istio resource creation to pass the *_PROXY environment variables when deploying Istio controller, and this is passed down to Gateway instances created by users. This configuration allows envoy proxies that rely on downloading WASMPlugins, on an air-gapped environment that enforces the usage of a network proxy, to download the artifacts using the network proxy.

openshift-merge-bot · 2026-07-22T16:40:34Z

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-07-22T16:40:40Z

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: ca8ed7a7-58a8-4971-9443-2733461bf113

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-ci-robot · 2026-07-22T16:41:44Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-77457 has been cloned as Jira Issue OCPBUGS-99476. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-99476: Respect proxy configuration on gwapi provisioning

Details

In response to this:

This is an automated cherry-pick of #1383

/assign rikatz

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-07-22T16:41:57Z

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

expected dependent Jira Issue OCPBUGS-77457 to target a version in 4.21.0, 4.21.z, but it targets "4.22.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 #1383

/assign rikatz

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.

rikatz · 2026-07-22T16:56:20Z

/jira refresh

openshift-ci-robot · 2026-07-22T16:56:25Z

@rikatz: This pull request references Jira Issue OCPBUGS-99476, which is invalid:

expected dependent Jira Issue OCPBUGS-77457 to target a version in 4.21.0, 4.21.z, but it targets "4.22.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.

rikatz · 2026-07-22T16:58:06Z

/jira refresh

openshift-ci-robot · 2026-07-22T16:58:10Z

@rikatz: This pull request references Jira Issue OCPBUGS-99476, which is invalid:

expected Jira Issue OCPBUGS-99476 to depend on a bug targeting a version in 4.21.0, 4.21.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

rikatz · 2026-07-28T14:01:06Z

/lgtm
/approve

openshift-merge-bot · 2026-07-28T14:04:20Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-operator
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-upgrade
/test e2e-azure-operator
/test e2e-azure-ovn
/test e2e-gcp-operator
/test e2e-hypershift

openshift-ci · 2026-07-28T14:05:04Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz

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

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

Miciah · 2026-07-29T14:45:01Z

/assign

redhat-chai-bot · 2026-08-01T02:54:55Z

Backport Risk Assessment — PR #1519 → `release-4.20`

Cherry-pick of #1383 (OCPBUGS-77457 → OCPBUGS-99476)

Overall: Low risk

Risk mitigants

4+ months of soak time — the parent fix landed in nightly 4.22.0-0.nightly-2026-03-23-022245 (March 2026) and shipped in RHEA-2026:0449. The code path is well exercised in 4.22.
No new RBAC required — proxies is already in the operator's ClusterRole on release-4.20 (00-cluster-role.yaml). This eliminates the HyperShift manifest-ordering concern that would apply if new RBAC had been introduced.
Three-layer graceful degradation — Proxy CR not found → no-op; empty fields → no metadata injected; nil guards at every call site. Clusters without a proxy config are completely unaffected.
Small, additive diff — +169/−23, confined to the GatewayClass controller. Both the OLM and Sail Library installation paths are updated symmetrically.
Clean automated cherry-pick — no merge conflicts, no manual adaptation.

Items to watch

CI — 12/16 checks pass (unit, verify, e2e-aws-ovn, e2e-hypershift, upgrade, etc.). Three failures remain: e2e-aws-operator, e2e-azure-ovn, and hypershift-e2e-aks. These should be confirmed as unrelated flakes before merge. (hypershift-e2e-aks also failed on the 4.21 backport [release-4.21] OCPBUGS-99453: Respect proxy configuration on gwapi provisioning #1518, suggesting a known flake on these branches.)
New watch source — the controller now watches configv1.Proxy (filtered to the cluster object). This adds one more informer to the GatewayClass controller. Low-risk since the Proxy CR is a singleton that rarely changes, but it does mean proxy changes will trigger a reconcile of every GatewayClass.

Assessment synthesized from #forum-ocp-network-edge thread discussion and prior analysis of PR #1518.

Miciah · 2026-08-01T02:55:20Z

/label backport-risk-assessed

melvinjoseph86 · 2026-08-01T10:23:30Z

/test e2e-vsphere-static-metallb-operator-gwapi
/retest-required

openshift-ci · 2026-08-01T13:08:35Z

@openshift-cherrypick-robot: 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/e2e-azure-ovn	`6ea1b8e`	link	false	`/test e2e-azure-ovn`
ci/prow/hypershift-e2e-aks	`6ea1b8e`	link	true	`/test hypershift-e2e-aks`

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.

melvinjoseph86 · 2026-08-01T17:43:13Z

➜  oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2026-08-01-102837-test-ci-ln-7y1xbbb-latest   True        False         36m     Cluster version is 4.20.0-0-2026-08-01-102837-test-ci-ln-7y1xbbb-latest

➜  oc -n openshift-ingress get pod    
NAME                                         READY   STATUS    RESTARTS      AGE
gateway-openshift-default-5cd549c9cc-t9nf4   0/1     Running   0             5s
istiod-openshift-gateway-9dbdfcf6c-fhv2b     1/1     Running   0             21s
router-default-76b95f8d89-4pwhb              1/1     Running   2 (51m ago)   61m
router-default-76b95f8d89-lrvzk              1/1     Running   2 (50m ago)   61m
➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                 PROGRAMMED   AGE
gateway   openshift-default   a67985dacb58246b2a3360f64d988ce4-63991867.us-west-1.elb.amazonaws.com   True         19s
➜  oc -n openshift-ingress get deployment gateway-openshift-default -oyaml | grep PROXY -A1
        - name: PROXY_CONFIG
          value: |
            {"discoveryAddress":"istiod-openshift-gateway.openshift-ingress.svc:15012","proxyMetadata":{"HTTPS_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","HTTP_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","NO_PROXY":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost","http_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","https_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","no_proxy":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost"},"proxyHeaders":{"server":{"disabled":true},"envoyDebugHeaders":{"disabled":true},"metadataExchangeHeaders":{"mode":"IN_MESH"}}}
        - name: ISTIO_META_POD_PORTS
--
        - name: HTTPS_PROXY
          value: http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
        - name: HTTP_PROXY
          value: http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
        - name: NO_PROXY
          value: .cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost

➜  oc  get pods -n openshift-ingress gateway-openshift-default-5cd549c9cc-t9nf4  -o jsonpath='{range .spec.containers[*].env[*]}{.name}{"="}{.value}{"\n"}{end}' |grep PROXY
PROXY_CONFIG={"discoveryAddress":"istiod-openshift-gateway.openshift-ingress.svc:15012","proxyMetadata":{"HTTPS_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","HTTP_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","NO_PROXY":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost","http_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","https_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","no_proxy":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost"},"proxyHeaders":{"server":{"disabled":true},"envoyDebugHeaders":{"disabled":true},"metadataExchangeHeaders":{"mode":"IN_MESH"}}}
HTTPS_PROXY=http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
HTTP_PROXY=http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
NO_PROXY=.cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost

Tried on proxy cluster and hence marking as verified
/verified by @mjoseph

openshift-ci-robot · 2026-08-01T17:43:23Z

@melvinjoseph86: This PR has been marked as verified by @mjoseph.

Details

In response to this:

➜  oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2026-08-01-102837-test-ci-ln-7y1xbbb-latest   True        False         36m     Cluster version is 4.20.0-0-2026-08-01-102837-test-ci-ln-7y1xbbb-latest

➜  oc -n openshift-ingress get pod    
NAME                                         READY   STATUS    RESTARTS      AGE
gateway-openshift-default-5cd549c9cc-t9nf4   0/1     Running   0             5s
istiod-openshift-gateway-9dbdfcf6c-fhv2b     1/1     Running   0             21s
router-default-76b95f8d89-4pwhb              1/1     Running   2 (51m ago)   61m
router-default-76b95f8d89-lrvzk              1/1     Running   2 (50m ago)   61m
➜  oc -n openshift-ingress get gateway
NAME      CLASS               ADDRESS                                                                 PROGRAMMED   AGE
gateway   openshift-default   a67985dacb58246b2a3360f64d988ce4-63991867.us-west-1.elb.amazonaws.com   True         19s
➜  oc -n openshift-ingress get deployment gateway-openshift-default -oyaml | grep PROXY -A1
       - name: PROXY_CONFIG
         value: |
           {"discoveryAddress":"istiod-openshift-gateway.openshift-ingress.svc:15012","proxyMetadata":{"HTTPS_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","HTTP_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","NO_PROXY":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost","http_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","https_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","no_proxy":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost"},"proxyHeaders":{"server":{"disabled":true},"envoyDebugHeaders":{"disabled":true},"metadataExchangeHeaders":{"mode":"IN_MESH"}}}
       - name: ISTIO_META_POD_PORTS
--
       - name: HTTPS_PROXY
         value: http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
       - name: HTTP_PROXY
         value: http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
       - name: NO_PROXY
         value: .cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost

➜  oc  get pods -n openshift-ingress gateway-openshift-default-5cd549c9cc-t9nf4  -o jsonpath='{range .spec.containers[*].env[*]}{.name}{"="}{.value}{"\n"}{end}' |grep PROXY
PROXY_CONFIG={"discoveryAddress":"istiod-openshift-gateway.openshift-ingress.svc:15012","proxyMetadata":{"HTTPS_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","HTTP_PROXY":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","NO_PROXY":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost","http_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","https_proxy":"http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/","no_proxy":".cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost"},"proxyHeaders":{"server":{"disabled":true},"envoyDebugHeaders":{"disabled":true},"metadataExchangeHeaders":{"mode":"IN_MESH"}}}
HTTPS_PROXY=http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
HTTP_PROXY=http://ci-ln-7y1xbbb-76ef8:3777155762b257d273e6e84c869410dc@10.0.15.45:3128/
NO_PROXY=.cluster.local,.svc,.us-west-1.compute.internal,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.ci-ln-7y1xbbb-76ef8.aws-2.ci.openshift.org,localhost

Tried on proxy cluster and hence marking as verified
/verified by @mjoseph

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.

redhat-chai-bot · 2026-08-01T17:45:20Z

Hi @openshift-ci-robot -- I can only respond automatically to comments from verified Red Hat associates.

Your GitHub account could not be confirmed. If you are a Red Hat employee and believe this is an error, please ask for help in the #chai-users Slack channel.

openshift-cherrypick-robot assigned rikatz Jul 22, 2026

openshift-cherrypick-robot mentioned this pull request Jul 22, 2026

OCPBUGS-77457: Respect proxy configuration on gwapi provisioning #1383

Merged

openshift-ci Bot requested review from bentito and knobunc July 22, 2026 16:41

openshift-ci Bot changed the title ~~[release-4.20] OCPBUGS-77457: Respect proxy configuration on gwapi provisioning~~ [release-4.20] OCPBUGS-99476: Respect proxy configuration on gwapi provisioning Jul 22, 2026

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

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

openshift-ci Bot assigned Miciah Jul 29, 2026

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

openshift-ci Bot assigned melvinjoseph86 and rhamini3 Aug 1, 2026

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

Uh oh!

Conversation

openshift-cherrypick-robot commented Jul 22, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 22, 2026

Uh oh!

coderabbitai Bot commented Jul 22, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Jul 22, 2026

Uh oh!

openshift-ci-robot commented Jul 22, 2026

Uh oh!

rikatz commented Jul 22, 2026

Uh oh!

openshift-ci-robot commented Jul 22, 2026

Uh oh!

rikatz commented Jul 22, 2026

Uh oh!

openshift-ci-robot commented Jul 22, 2026

Uh oh!

rikatz commented Jul 28, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 28, 2026

Uh oh!

openshift-ci Bot commented Jul 28, 2026

Uh oh!

Miciah commented Jul 29, 2026

Uh oh!

redhat-chai-bot commented Aug 1, 2026

Backport Risk Assessment — PR #1519 → release-4.20

Risk mitigants

Items to watch

Uh oh!

Miciah commented Aug 1, 2026

Uh oh!

melvinjoseph86 commented Aug 1, 2026

Uh oh!

openshift-ci Bot commented Aug 1, 2026

Uh oh!

melvinjoseph86 commented Aug 1, 2026

Uh oh!

openshift-ci-robot commented Aug 1, 2026

Uh oh!

redhat-chai-bot commented Aug 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

Backport Risk Assessment — PR #1519 → `release-4.20`