Using Traefik

  • Tier: Free, Premium, Ultimate
  • Offering: GitLab Self-Managed

The bundled Traefik chart was deprecated in GitLab 18.9 and is planned for removal in GitLab 20.0. This change is a breaking change.

Before you upgrade to GitLab 20.0, migrate to the bundled Envoy Gateway or deploy Traefik as an external Ingress controller.

The GitLab chart bundles the Traefik Helm chart as an optional Ingress controller. The bundled Traefik chart is disabled by default. Since GitLab 19.0, the chart defaults to Gateway API with the bundled Envoy Gateway.

Traefik will translate the native Kubernetes Ingress objects into IngressRoute objects.

Traefik also supports Git over SSH via IngressRouteTCP objects, which are deployed by the GitLab Shell chart when global.ingress.provider is configured as traefik.

Configuring Traefik

See the Traefik Helm chart documentation for configuration details.

See the Traefik 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 Traefik

Traefik Enterprise provides FIPS compliance. Note that Traefik Enterprise requires a license, which is not included as part of this chart.

Following are links for more information on Traefik Enterprise: