feat(ci): remove vcluster/EKS trigger jobs; keep one GKE nightly
What does this MR do?
Once the k3d matrix (!4967 (merged)–!4983 (merged)) is proven stable: removes all vcluster environments and the trigger_review_* manual gates, keeping a single GKE nightly job using GCP's stable release channel (auto-upgrades K8s — no vcluster needed).
Removes:
- All vcluster environment configs (
.gitlab/ci/environments/vcluster.*.yml) trigger_review_currentandtrigger_review_secondarymanual gate jobs- Per-version vcluster trigger jobs (
trigger-v133,trigger-v134,trigger-v135, etc.) - EKS native environment (
.gitlab/ci/environments/eks.134.amd64.gitlab-ci.yml) vcluster-review-apps.gitlab-ci.ymlbase template
Keeps:
- One scheduled nightly GKE v1.35 job (real cloud provider validation, GCP manages node upgrades)
WIP — implementation pending. Will be fleshed out once !4983 (merged) is merged.
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) | Complete |
| 2 | !4984 (merged) | Switch networking to Envoy Gateway API | Complete |
| 3 | !4982 (merged) | Extend K8s version matrix (v1.33, v1.34, v1.35 ARM64) | Complete |
| 4 | !4983 (merged) | Add manual full suite QA jobs | Complete |
| 5 | !4985 (merged) | Remove vcluster/EKS environments | We are here |
Each MR targets the previous branch and is blocked by it (see MR dependencies).
Related issues
Closes #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 Jason Plum