Configuring HAProxy
- Global Settings
- FIPS-compliant HAProxy

Using HAProxy

The HAProxy Helm Chart can replace the bundled NGINX Helm chart as the Ingress controller, and is documented in Kubernetes’ list of additional Ingress controllers.

HAProxy will also support Git over SSH.

We default to NGINX mostly due to historical experience with the tool, but HAProxy is a valid alternative that may be preferable to those who have more experience with HAProxy specifically. Additionally, it offers FIPS compliance while the NGINX Ingress controller currently does not.

Configuring HAProxy

See the HAProxy Helm chart documentation or the Helm values file. for configuration details.

See the HAProxy example configuration for detailed YAML for values tested with the GitLab Helm Charts.

Global Settings

We share some common global settings among our charts. See the Global Ingress documentation for common configuration options, such as GitLab and Registry hostnames.

FIPS-compliant HAProxy

HAProxy Enterprise provides FIPS compliance. Note that HAProxy Enterprise requires a license.

Following are links for more information on HAProxy Enterprise:

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support