Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(expect-proxy): provide alternative health endpoint for expect_proxy_cidrs #717

Merged
merged 2 commits into from
Oct 31, 2024

Conversation

peanball
Copy link
Contributor

expect_proxy_cidrs is used for dynamically determining whether proxy protocol should be used or not. On AWS the health check and regular traffic are forwarded with or without proxy protocol.

The idea of adding the expect-proxy directive CIDRs for AWS load balancer IP addresses as a "marker" for traffic that should become Proxy Protocol, while other traffic (including transparently proxied traffic) remains without Proxy Protocol.

By adding a new health endpoint, when expect_proxy_cidrs is set, the operator can select, which endpoint to use for checking the health of HAProxy.

…xy_cidrs

`expect_proxy_cidrs` is used for dynamically determining whether proxy protocol should be used or not.
On AWS the health check and regular traffic are forwarded with or without proxy protocol.

The idea of adding the `expect-proxy` directive CIDRs for AWS load balancer
IP addresses as a "marker" for traffic that should become Proxy Protocol, while
other traffic (including transparently proxied traffic) remains without
Proxy Protocol.

By adding a new health endpoint, when `expect_proxy_cidrs` is set, the
operator can select, which endpoint to use for checking the health of
HAProxy.
@peanball peanball requested review from CFN-CI and a team as code owners October 28, 2024 15:45
@peanball peanball added the run-ci Allow this PR to be tested on Concourse label Oct 28, 2024
@peanball peanball force-pushed the expect_proxy_health_endpoint branch 3 times, most recently from 06ce19d to 5b7ffb1 Compare October 29, 2024 14:24
When `expect_proxy_cidrs` is set, the health check endpoints work as follows:
* 8080 (`health_check_port`): the health check endpoint works via regular HTTP
* 8081 (`health_check_port` + 1): the alternative health check endpoint works only with Proxy Protocol

Operators can then select, which endpoint they want to use in accordance
with their `expect_proxy_cidrs` settings.
@peanball peanball enabled auto-merge (rebase) October 31, 2024 14:54
@peanball peanball merged commit b72bdae into master Oct 31, 2024
4 checks passed
@peanball peanball deleted the expect_proxy_health_endpoint branch October 31, 2024 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run-ci Allow this PR to be tested on Concourse
Projects
Development

Successfully merging this pull request may close these issues.

2 participants