Skip to content

ART-21453: Add image config for ose-haproxy-router-haproxy32#11725

Merged
openshift-merge-bot[bot] merged 3 commits into
openshift-eng:openshift-5.0from
ashwindasr:add-ose-haproxy-router-haproxy32
Jul 13, 2026
Merged

ART-21453: Add image config for ose-haproxy-router-haproxy32#11725
openshift-merge-bot[bot] merged 3 commits into
openshift-eng:openshift-5.0from
ashwindasr:add-ose-haproxy-router-haproxy32

Conversation

@ashwindasr

@ashwindasr ashwindasr commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Add new image configuration for ose-haproxy-router-haproxy32 to the OCP 5.0 build data.

HAProxy 3.2 is being deployed as a sidecar of the router pod as part of OCPSTRAT-2943, mirroring the ose-haproxy-router-haproxy28 config added in ART-21452 (#11561, #11643).

Details

  • Component: containers/haproxy-router-haproxy32
  • Payload name: haproxy-router-haproxy32
  • Image type: CVO payload (for_payload: true)
  • Source: openshift/router/images/router/haproxy32/Dockerfile.ocp
  • Delivery repo: openshift5/ose-haproxy-router-haproxy32-rhel9
  • Bug component: Networking / router
  • Approval: NE-2218 comment
  • Jira: ART-21453

Includes the okd: block from the start (haproxy28 needed a follow-up PR #11643 for this).

delivery_repo_names uses the -rhel9 suffix to match how the delivery repo is actually registered in Pyxis (see pyxis-repo-configs MR !1117). The equivalent fix for haproxy28 is in #11726.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 8, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 8, 2026

Copy link
Copy Markdown

@ashwindasr: This pull request references ART-21453 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 "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Add new image configuration for ose-haproxy-router-haproxy32 to the OCP 5.0 build data.

HAProxy 3.2 is being deployed as a sidecar of the router pod as part of OCPSTRAT-2943, mirroring the ose-haproxy-router-haproxy28 config added in ART-21452 (#11561, #11643).

Details

  • Component: containers/haproxy-router-haproxy32
  • Payload name: haproxy-router-haproxy32
  • Image type: CVO payload (for_payload: true)
  • Source: openshift/router/images/router/haproxy32/Dockerfile.ocp
  • Delivery repo: openshift5/ose-haproxy-router-haproxy32
  • Bug component: Networking / router
  • Approval: NE-2218 comment
  • Jira: ART-21453

Includes the okd: block from the start (haproxy28 needed a follow-up PR #11643 for 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.

@ashwindasr

Copy link
Copy Markdown
Contributor Author

/test art-konflux-delivery-repo-check

Add new image configuration for ose-haproxy-router-haproxy32 to the
OCP 5.0 build data. HAProxy 3.2 is being deployed as a sidecar of the
router pod as part of OCPSTRAT-2943, mirroring the haproxy28 config
added in ART-21452.

Co-authored-by: Cursor <cursoragent@cursor.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
The Pyxis delivery repo is registered as openshift5/ose-haproxy-router-haproxy32-rhel9 (see pyxis-repo-configs), so delivery_repo_names must match.

Co-authored-by: Cursor <cursoragent@cursor.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@ashwindasr ashwindasr force-pushed the add-ose-haproxy-router-haproxy32 branch from 921469d to 828b632 Compare July 8, 2026 19:34
@ashwindasr ashwindasr added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jul 8, 2026
@ashwindasr

Copy link
Copy Markdown
Contributor Author

/test art-konflux-delivery-repo-check

…entOS Stream 9 base

Without okd.from.stream: centos_stream9, the OKD build inherits a
CentOS Stream 10 base through openshift-enterprise-base-rhel9's OKD
override (okd.distgit.branch: rhaos-5.0-rhel-10). The haproxy32 RPM
from rhel-9-server-ose-rpms is an el9 package that requires libpcre.so.1
(PCRE1), which was removed in CentOS/RHEL 10.

Mirrors the fix applied to ose-haproxy-router-haproxy28 (openshift-eng#11759) and
the pattern used by ose-haproxy-router-base.

Co-authored-by: Cursor <cursoragent@cursor.com>

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@pruan-rht

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 13, 2026
@rayfordj

Copy link
Copy Markdown
Contributor

/lgtm
/approve
/label tide/merge-method-squash

@openshift-ci

openshift-ci Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pruan-rht, rayfordj

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:

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

@rayfordj rayfordj added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jul 13, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 3395f64 into openshift-eng:openshift-5.0 Jul 13, 2026
4 checks passed
@ashwindasr ashwindasr deleted the add-ose-haproxy-router-haproxy32 branch July 14, 2026 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants