Remove PostgreSQL 13
What does this MR do?
Remove PostgreSQL 13
- Remove PostgreSQL 13 builds.
- Remove unused PostgreSQL 12 build definition.
- Move PostgreSQL 14 from 'new' to 'default' build definition.
- Update minimum PostgreSQL version notice.
- Disable automatic PostgreSQL upgrades.
Changelog: removed
Notes:
- Non HA instances will be upgraded automatically to Pg 14 with Omnibus 16.11 (if they did not opt out).. HA instances will need to upgrade manually before the upgrade.
- The deprecation was announced in gitlab!119996 (diffs).
Related issues
Closes #8341
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
Latest Merge Result pipeline is green. -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
-
The manual Trigger:ee-package
jobs have a green pipeline running against latest commit. -
If config/software
orconfig/patches
directories are changed, make sure thebuild-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, then theTrigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline must succeed. -
If CI configuration is changed, the branch must be pushed todev.gitlab.org
to confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. gitlab!149539 (merged) -
Tests added. -
Integration tests added to GitLab QA. -
Equivalent MR/issue for the GitLab Chart opened. -
Validate potential values for new configuration settings. Formats such as integer10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Clemens Beck