Skip to content

WIP: haproxy-config.template: Use PROXY protocol v2#391

Open
Miciah wants to merge 1 commit intoopenshift:masterfrom
Miciah:haproxy-config-dot-template-use-PROXY-protocol-v2
Open

WIP: haproxy-config.template: Use PROXY protocol v2#391
Miciah wants to merge 1 commit intoopenshift:masterfrom
Miciah:haproxy-config-dot-template-use-PROXY-protocol-v2

Conversation

@Miciah
Copy link
Copy Markdown
Contributor

@Miciah Miciah commented May 25, 2022

  • images/router/haproxy/conf/haproxy-config.template: Use PROXY protocol v2 for the internal "be_sni" and "be_no_sni" backends and "fe_no_sni" and "fe_sni" frontends.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 25, 2022
@openshift-ci openshift-ci Bot requested review from alebedev87 and frobware May 25, 2022 22:51
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 25, 2022
@Miciah Miciah force-pushed the haproxy-config-dot-template-use-PROXY-protocol-v2 branch from eafd0ab to bd37a97 Compare May 25, 2022 22:51
* images/router/haproxy/conf/haproxy-config.template: Use PROXY protocol v2
for the internal "be_sni" and "be_no_sni" backends and "fe_no_sni" and "fe_sni"
frontends.
@Miciah Miciah force-pushed the haproxy-config-dot-template-use-PROXY-protocol-v2 branch from bd37a97 to c755f04 Compare May 25, 2022 23:01
@openshift-bot
Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 24, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 24, 2022
@openshift-bot
Copy link
Copy Markdown
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Oct 24, 2022
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Oct 24, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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/test-infra repository.

@Miciah
Copy link
Copy Markdown
Contributor Author

Miciah commented Apr 27, 2026

/reopen

@openshift-ci openshift-ci Bot reopened this Apr 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

@Miciah: Reopened this PR.

Details

In response to this:

/reopen

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-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 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 davidesalerno 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

@openshift-ci openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 27, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 27, 2026

@Miciah: 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.

@jcmoraisjr
Copy link
Copy Markdown
Member

Looks a fair update and it is currently in a good timing (start of a new release). It marginally improves performance and should not have any backward incompatibility - HAProxy itself is handling the changed request, and a proxy-proto aware frontend handles both v1 and v2.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2026
@Miciah
Copy link
Copy Markdown
Contributor Author

Miciah commented May 6, 2026

I still need to create a Jira tracker for this PR.

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants