Help us learn about your current experience with the documentation. Take the survey.

Use Gateway API and Envoy Gateway

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

Before enabling Gateway API with the Operator check the GitLab chart Gateway API documentation for details on the available configuration options and current limitations.

Starting with Operator 2.10 and GitLab chart 9.7, GitLab can be exposed by using Gateway API instead of Ingress. This follows the Kubernetes community recommendation after the NGINX Ingress retirement.

Prerequisites

The GitLab Operator does not bundle a Gateway API controller like GitLab chart does. Before exposing a GitLab instance managed by the Operator through Gateway API, you must first install a Gateway API implementation such as Envoy Gateway.

If you use the GitLab chart 10.3 or newer and the official Envoy Gateway Helm chart, deploy Envoy Gateway 1.9 for compatibility with the TCPRoute v1 API. If your Gateway API implementation does not support TCPRoute v1 yet, override the rendered API version by setting gitlab.gitlab-shell.gatewayRoute.apiVersion=gateway.networking.k8s.io/v1alpha2 in the chart values.

If you intend to manage TLS certificates with certmanager, make sure to configure it for Gateway API.