Skip to content

NE-2664: add opt-in config to deploy haproxy as sidecar#1439

Open
jcmoraisjr wants to merge 1 commit intoopenshift:masterfrom
jcmoraisjr:NE-2664-haproxy-sidecar
Open

NE-2664: add opt-in config to deploy haproxy as sidecar#1439
jcmoraisjr wants to merge 1 commit intoopenshift:masterfrom
jcmoraisjr:NE-2664-haproxy-sidecar

Conversation

@jcmoraisjr
Copy link
Copy Markdown
Member

An opt-in configuration adds HAProxy as a sidecar container. This is a first but fully functional implementation that allows starting e2e and exploratory tests using the new topology.

Key differences from a final version:

  • The same image is used both on router and haproxy containers; and
  • It is not possible to select HAProxy version.

This is due to some other and still pending stories that will handle both a new API field and building HAProxy image for all supported versions.

Note for testers: add 'haproxy-sidecar: "1"' annotation in the IngressController resource. This should create router pod with two containers, and it should behave in the same way as before.

https://redhat.atlassian.net/browse/NE-2664

An opt-in configuration adds HAProxy as a sidecar container. This is a
first but fully functional implementation that allows starting e2e and
exploratory tests using the new topology.

Key differences from a final version:

* The same image is used both on router and haproxy containers; and
* It is not possible to select HAProxy version.

This is due to some other and still pending stories that will handle
both a new API field and building HAProxy image for all supported
versions.

Note for testers: add 'haproxy-sidecar: "1"' annotation in the
IngressController resource. This should create router pod with two
containers, and it should behave in the same way as before.

https://redhat.atlassian.net/browse/NE-2664
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 7, 2026

@jcmoraisjr: This pull request references NE-2664 which is a valid jira issue.

Details

In response to this:

An opt-in configuration adds HAProxy as a sidecar container. This is a first but fully functional implementation that allows starting e2e and exploratory tests using the new topology.

Key differences from a final version:

  • The same image is used both on router and haproxy containers; and
  • It is not possible to select HAProxy version.

This is due to some other and still pending stories that will handle both a new API field and building HAProxy image for all supported versions.

Note for testers: add 'haproxy-sidecar: "1"' annotation in the IngressController resource. This should create router pod with two containers, and it should behave in the same way as before.

https://redhat.atlassian.net/browse/NE-2664

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 frobware and gcs278 May 7, 2026 16:06
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 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 gcs278 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

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 7, 2026

Warning

Rate limit exceeded

@jcmoraisjr has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 45 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 25d105d8-6bbf-4232-9ba0-b74946a9c416

📥 Commits

Reviewing files that changed from the base of the PR and between b2e0220 and 43c46e2.

📒 Files selected for processing (3)
  • pkg/manifests/assets/router/deployment.yaml
  • pkg/operator/controller/ingress/deployment.go
  • pkg/operator/controller/ingress/deployment_test.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

@jcmoraisjr: 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-aws-operator-techpreview 43c46e2 link false /test e2e-aws-operator-techpreview
ci/prow/e2e-aws-ovn-serial-2of2 43c46e2 link true /test e2e-aws-ovn-serial-2of2
ci/prow/hypershift-e2e-aks 43c46e2 link true /test hypershift-e2e-aks
ci/prow/e2e-aws-ovn-serial-1of2 43c46e2 link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-gcp-operator 43c46e2 link true /test e2e-gcp-operator
ci/prow/e2e-aws-ovn 43c46e2 link true /test e2e-aws-ovn
ci/prow/e2e-aws-ovn-hypershift-conformance 43c46e2 link true /test e2e-aws-ovn-hypershift-conformance
ci/prow/e2e-aws-ovn-upgrade 43c46e2 link true /test e2e-aws-ovn-upgrade
ci/prow/e2e-azure-operator 43c46e2 link true /test e2e-azure-operator

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.

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.

2 participants