Migrate CI build from Debian bookworm to trixie

Stan Hurequested to merge
debian-bookworm-to-trixie into master

What does this MR do?

Move the CI build from Debian bookworm (Debian 12) to trixie (Debian 13), following the corresponding CNG/build-images moves. The initial DEBIAN_VERSION flip surfaced several image-tag and package-version mismatches, which this MR also fixes so the pipeline is green on trixie.

Debian version bump

  • .gitlab-ci.yml: DEBIAN_VERSION bookworm-slim -> trixie-slim.
  • scripts/ci/install_spec_dependencies.sh: DEBIAN_VERSION_NUMBER 12 -> 13, DEBIAN_VERSION default bookworm -> trixie.
  • Docs: Debian manpage links updated from bookworm/bullseye to trixie (English + fr/ja/ko).

CI image tags

The trixie build-images pin different tool versions than the old bookworm images, so the referenced tags did not exist and jobs failed to pull:

  • chart-base image (kubeconform, lint_chart, and other default jobs): kubectl 1.33 -> 1.35, awscli 1.40.35 -> 1.44.59.
  • specs image (rspec): the trixie CI image drops Go 1.24 and Chrome 133, so the .specs job overrides GO_VERSION to 1.25 and CHROME_VERSION to 151, a combination that is actually published.

Ruby version

Docker package version

  • DOCKER_VERSION 28.0.1 -> 28.1.0. Docker's trixie apt repository has no 28.0.1 build; 28.1.0 is the lowest available and exists for bookworm too.

All referenced image tags and package versions were verified against the GitLab container registry and the Docker apt repository.

Related issues

Relates to gitlab-org/build/CNG#2374 (closed)

Follows:

Author checklist

  • 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.
  • Have you validated that your change works end-to-end on a real cluster deployment?
  • Equivalent MR/issue for omnibus-gitlab opened.
Edited by Lucas Li

Merge request reports