Configure the GitLab chart with an external Ingress Controller

Since GitLab 19.0, the chart defaults to Gateway API with the bundled Envoy Gateway. The bundled NGINX Ingress, HAProxy, and Traefik charts are deprecated and planned for removal in GitLab 20.0. You can keep using Ingresses with an external Ingress controller.

Prepare the external Ingress controller

NGINX

NGINX Ingress was deprecated and won’t receive security patches after March 2026. Read the official announcement for more information.

Check the external NGINX Ingress documentation to configure and prepare a external NGINX Ingress deployment to be used with GitLab.

Traefik

Traefik must be configured to expose port 22 for GitLab Shell (GitLabs SSH daemon):

yaml
ports:
  gitlab-shell:
    expose: true
    port: 2222
    exposedPort: 22

Customize the GitLab Ingress options

The NGINX Ingress Controller uses an annotation to mark which Ingress Controller will service a particular Ingress (see docs). You can configure the Ingress class to use with this chart using the global.ingress.class setting. Make sure to set this in your Helm options.

shell
--set global.ingress.class=myingressclass

Enable the chart Ingress resources:

shell
--set global.ingress.enabled=true

The bundled NGINX Ingress controller is disabled by default since GitLab 19.0. If you enabled it before, disable it:

shell
--set nginx-ingress.enabled=false

Custom certificate management

If you are using an external Ingress Controller, you may also be using an external cert-manager instance or managing your certificates in some other custom manner. For full documentation about your TLS options, see configure TLS for the GitLab chart, however for the purposes of this discussion, here are the two values that would need to be set to disable the cert-manager chart and tell the GitLab component charts to not look for the built in certificate resources:

shell
--set installCertmanager=false
--set global.ingress.configureCertmanager=false