fix(e2e): disable envoy-gateway to allow concurrent runs

Why

E2E jobs running concurrently against the shared GKE harness collide on cluster-scoped resources installed by the GitLab chart's bundled envoy-gateway. Helm tags those resources with meta.helm.sh/release-namespace=e2e-<sha>-gitlab, so the second concurrent run fails with:

ClusterRole gitlab-envoy-gateway-envoy-gateway-role exists and cannot be imported into the current release

Example failure: job 14453149579 (SHA d5d52164) failed while job 14453129851 (SHA dff71d1c) was holding the resources.

What

Disable bundled envoy-gateway in e2e/values/gitlab.yaml.gotmpl:

global:
  gatewayApi:
    enabled: false
    installEnvoy: false

Why this is safe

Nothing in the e2e suite reaches GitLab through a gateway/ingress:

  • e2e/charts/robot-runner/templates/job.yaml uses GITLAB_URL=http://gitlab-webservice-default.<ns>.svc.cluster.local:8181 (direct Service)
  • e2e/values/gitlab.yaml.gotmpl already disables global.ingress.enabled, nginx-ingress.enabled, global.hosts.https
  • envoy-gateway is the chart's optional Gateway-API alternative to nginx-ingress; nothing internal depends on it

Merge request reports

Loading
Loading