gitlab update to 10.1.3-bb.0

Package Merge Request

Package Changes

https://repo1.dso.mil/big-bang/product/packages/gitlab/-/blob/10.1.3-bb.0/CHANGELOG.md

Package MR

big-bang/product/packages/gitlab!473 (merged)

For Issue

Closes big-bang/product/packages/gitlab#412 (closed)

Upgrade Notices

GitLab 19 / chart 10 removes the bundled PostgreSQL, Redis, and MinIO charts. Helm does not migrate their data.

• Consumers using any bundled service must remain on the latest GitLab 18.11 / chart 9.11 patch while following GitLab's bundled-chart migration procedure. Verify GitLab and a fresh backup against the replacement services before upgrading to chart 10. Retain the old PVCs, Secrets, and recovery artifacts until GitLab 19 and a new backup are verified.

• Consumers already using GitLab 19-compatible external PostgreSQL 17, Redis 7.0 or later (7.2 recommended) or Valkey 7.2 or later, and GitLab-supported external object storage do not need a service-data migration solely because the bundled charts were removed. They must still complete the normal GitLab 19 pre-upgrade checks, verify every external connection and bucket, finish pending migrations, and take a fresh verified backup.

• This package does not deploy or support replacement PostgreSQL, Redis/Valkey, object-storage, or CloudNativePG resources for consumers. Configure GitLab-supported external services before upgrading. If CloudNativePG is selected, install and manage the Big Bang maintained CloudNativePG operator before creating the PostgreSQL Cluster; its lifecycle remains outside this GitLab package. For production, follow GitLab's Cloud Native Hybrid guidance.

• Build clean chart 10 values instead of reusing chart 9 values. Remove obsolete global.minio, upstream.minio, upstream.postgresql, and upstream.redis keys while retaining every supported override. In particular, preserve the existing Gitaly persistence size because the StatefulSet volume-claim template is immutable. Render and diff the chart 10 StatefulSets before reconciling.

• Follow the Big Bang-specific GitLab 19 upgrade notes. Inventory all optional databases and object-storage buckets because the default GitLab backup does not cover every site-specific data store. Once GitLab 19 database migrations run, do not start GitLab 18 against that database; rollback requires matching GitLab, database, and object-storage recovery points.

• GitLab 19 removes the OAuth Resource Owner Password Credentials grant. Replace integrations using that grant before upgrading. If bundled Spamcheck is enabled, deploy Spamcheck separately. GitLab 19.1 also drops Elasticsearch 7.x support for Advanced Search; move to a supported Elasticsearch or OpenSearch release first.

• Consumers using a service account to pull GitLab application images from Iron Bank may need to verify access with Iron Bank, as GitLab 19 moves these images to the Verified Publisher CNG repository under registry1.dso.mil/gitlab/gitlab-org/build/cng/*. No separate application or data migration is required, but Registry1 credentials, mirrors, policies, and allowlists must permit access to the new image path.

• Review the GitLab 19 breaking changes, deprecations and removals, chart 10 upgrade notes, and GitLab 19 upgrade changes for site-specific impacts.

• This version has been superseded by gitlab update to 10.2.4-bb.0