ci(k3d): switch networking from NGINX ingress to Envoy Gateway
What does this MR do?
Replaces the NGINX ingress controller with Envoy Gateway (Gateway API) in all k3d environments. Uses HTTPRoute for HTTP traffic and TCPRoute for SSH (git-over-SSH specs).
What's added:
scripts/ci/values/gitlab-chart/k3d.gatewayapi.values.yaml— Helm values overriding ingress to use Gateway API
WIP — needs end-to-end validation with the full spec suite.
Implementation plan
This MR is part of a sequenced implementation. See issue #6421 for the full context and rationale.
| # | MR | Description | Status |
|---|---|---|---|
| 1 | !4967 (merged) | k3d PoC — single environment (v1.35 amd64, NGINX ingress) | In review |
| 2 | !4984 (merged) | Switch networking to Envoy Gateway API | In Review |
| 3 | !4982 (merged) | Extend K8s version matrix (v1.33, v1.34, v1.35 ARM64) | Draft |
| 4 | !4983 (merged) | Add manual full suite QA jobs | Draft |
| 5 | !4985 (merged) | Remove vcluster/EKS environments | Draft (WIP) |
Each MR targets the previous branch and is blocked by it (see MR dependencies).
Related issues
Part of #6421
Author checklist
For general guidance, please follow our Contributing guide.
Required
- Merge Request Title and Description are up to date, accurate, and descriptive.
- MR targeting the appropriate branch.
- MR has a green pipeline.
- Documentation created/updated.
- Tests added/updated, and test plan for scenarios not covered by automated tests.
- Equivalent MR/issue for omnibus-gitlab opened.
Reviewers checklist
- MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab.
- Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.
Edited by João Alexandre Cunha