Support deploying GitLab to Kubernetes 1.36

Grigoris Thanasoulasrequested to merge
grigoristh/support-k8s-1.36 into master

What does this MR do?

Adds support for deploying GitLab to Kubernetes 1.36 and rolls the supported-version window forward to 1.34–1.36 (deprecating 1.33, dropping 1.32), per the Kubernetes release support policy.

Changes (one commit each):

  • k3d CI matrix (.gitlab-ci.yml): drop v1.33, add v1.36.2 as the primary (auto-run) version, and refresh the retained versions to their latest patches (v1.34.9, v1.35.6); bump the k3d_arm64 and k3d_nginx jobs to v1.36.2. Version-slug references in the k3d child-pipeline comments updated accordingly.
  • kubeconform matrix (.gitlab/ci/kubeconform.gitlab-ci.yml): validate against 1.33.13 / 1.34.9 / 1.35.6 / 1.36.2, and bump the Helm 3.20 entry to 1.36.2.
  • Supported-releases docs (doc/installation/cloud/_index.md): add 1.36 (Supported, minimum GitLab 19.4), deprecate 1.33, mark 1.32 Unsupported, drop 1.31.

Removed APIs: none required. Kubernetes 1.36 removes no served API versions used by the chart (audited against the 1.36 changelog). The only relevant change is a deprecation warning on Service .spec.externalIPs — not removed, no removal date; being tracked separately in #6589 as a future-migration watch item.

Related issues

Related to gitlab-org/distribution/team-tasks#1829

Author checklist

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch (master).
  • MR has a green pipeline.
  • Documentation created/updated.
  • Tests added/updated.
  • Have you validated that your change works end-to-end on a real cluster deployment?
    • The k3d v136 child pipeline (LIMIT_TO=k3d_version, primary) deploys the chart on Kubernetes 1.36 and runs the review specs; the kubeconform job validates manifests against 1.36.
  • Equivalent MR/issue for omnibus-gitlab opened.

Reviewers checklist

Edited by Nailia Iskhakova

Merge request reports