Add net bind capability to haproxy bin #1096
Merged
+6
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HAProxy Ingress starts now as the non privileged user haproxy, and this is the same user that starts the embedded haproxy process. Some container runtimes do not configure the unprivileged_port_start param from the default 1024 to 0, which makes the embedded haproxy process fail to bind to 80/443 ports. Adding the net bind capability to the haproxy binary allows it to bind to any tcp port, without running as a privileged user, and without configuring unprivileged_port_start param.