Skip to content

NE-2215: add enhancement for selectable HAProxy version#1965

Open
jcmoraisjr wants to merge 1 commit intoopenshift:masterfrom
jcmoraisjr:NE-2215-select-haproxy-version
Open

NE-2215: add enhancement for selectable HAProxy version#1965
jcmoraisjr wants to merge 1 commit intoopenshift:masterfrom
jcmoraisjr:NE-2215-select-haproxy-version

Conversation

@jcmoraisjr
Copy link
Copy Markdown
Member

This enhancement proposes adding the ability for cluster administrators to select specific HAProxy versions for IngressControllers, decoupling HAProxy version upgrades from OpenShift cluster upgrades. Supports current release and up to 2 previous releases to facilitate LTS-to-LTS migrations.

Jira: https://redhat.atlassian.net/browse/NE-2215

This enhancement proposes adding the ability for cluster administrators to
select specific HAProxy versions for IngressControllers, decoupling HAProxy
version upgrades from OpenShift cluster upgrades. Supports current release
and up to 2 previous releases to facilitate LTS-to-LTS migrations.

Jira: https://redhat.atlassian.net/browse/NE-2215

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 1, 2026

@jcmoraisjr: This pull request references NE-2215 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 epic to target either version "4.22." or "openshift-4.22.", but it targets "openshift-5.0" instead.

Details

In response to this:

This enhancement proposes adding the ability for cluster administrators to select specific HAProxy versions for IngressControllers, decoupling HAProxy version upgrades from OpenShift cluster upgrades. Supports current release and up to 2 previous releases to facilitate LTS-to-LTS migrations.

Jira: https://redhat.atlassian.net/browse/NE-2215

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 openshift-ci bot requested review from knobunc and rfredette April 1, 2026 22:31
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 1, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign miciah for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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


This enhancement modifies an existing CRD (IngressController) but does not
add webhooks or aggregated API servers. The existing SLIs for
IngressController resources apply:
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if having a webhook instead is preferable, denying any attempt for an invalid requests. It needs a webhook since that in the current proposal the validation changes on every OpenShift release.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 1, 2026

@jcmoraisjr: The following test 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/markdownlint 1a89f0c link true /test markdownlint

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.


### Implementation Details/Notes/Constraints

The implementation requires the following high-level code changes:
Copy link
Copy Markdown
Member Author

@jcmoraisjr jcmoraisjr Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing high-level comment about the approaches to package HAProxy and isolate its dynamic dependencies. Wondering if it fits here to comment all the possibilities, choosing one of them later when starting to implement.

@davidesalerno
Copy link
Copy Markdown

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants