📚 Sync docs from alaudadevops/gitlab-ce-operator on b95aade853b7e19ff02c340ff6d0d7721b2c2f24

Source: docs: update PostgreSQL requirements and upgrade instructions (#248)
Author: nanjingfm
Ref: refs/heads/release-18.2
Commit: b95aade853b7e19ff02c340ff6d0d7721b2c2f24

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: AlaudaDevops/gitlab-ce-operator@b95aade
🤖 Synced on 2025-10-20 03:29:11 UTC

Author: nanjingfm

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-10-17 08:58:27 UTC
+- **Last synced**: 2025-10-20 03:29:11 UTC
 - **Source repository**: alaudadevops/gitlab-ce-operator
-- **Source commit**: [84b3e4418de660342b01bc06b6320ee8bab2b65c](https://github.com/alaudadevops/gitlab-ce-operator/commit/84b3e4418de660342b01bc06b6320ee8bab2b65c)
+- **Source commit**: [b95aade853b7e19ff02c340ff6d0d7721b2c2f24](https://github.com/alaudadevops/gitlab-ce-operator/commit/b95aade853b7e19ff02c340ff6d0d7721b2c2f24)
 - **Triggered by**: nanjingfm
-- **Workflow run**: [#40](https://github.com/alaudadevops/gitlab-ce-operator/actions/runs/18587808190)
+- **Workflow run**: [#41](https://github.com/alaudadevops/gitlab-ce-operator/actions/runs/18641185188)
 
 ## Files synced:
 - docs/

docs/en/install/02_gitlab_credential.mdx

@@ -108,12 +108,18 @@ Redis service can be provided by Alauda Cache Service for Redis OSS. In some spe
 
 ## PostgreSQL Credentials \{#pg-credentials}
 
-### Requirements
+### Requirements \{#pg-requirements}
 
 GitLab has the following requirements for PostgreSQL versions:
 
-- GitLab 17.z requires PostgreSQL version 14.z
-- GitLab 18.z requires PostgreSQL version 16.z
+| GitLab Version | Supported PostgreSQL Versions |
+| --------------- | ----------------------------- |
+| 17.z            | 14、16                          |
+| 18.z            | 16、17                          |
+
+::: info
+When upgrading GitLab to a new version, you need to upgrade the PostgreSQL version to meet the requirements for the new GitLab version.
+:::
 
 ### Credential Format
 

docs/en/upgrade/01_upgrade.mdx

@@ -16,11 +16,11 @@ You can read the [official upgrade documentation](https://docs.gitlab.com/update
 
 The table below contains the complete upgrade path. When upgrading, you need to upgrade the Operator and GitLab instance versions in sequence.
 
-| No  | Alauda Build of GitLab Operator Version |
-| --- | ---------------- |
-| 1   | 17.8.z           |
-| 2   | 17.11.z          |
-| 3   | 18.2.z          |
+| No  | Alauda Build of GitLab Operator Version | Requirements |
+| --- | ---------------- | ----------------------------- |
+| 1   | 17.8.z           | -               |
+| 2   | 17.11.z          | -               |
+| 3   | 18.2.z          | [**PostgreSQL 16** (upgrade required)](../install/02_gitlab_credential.mdx#pg-requirements)  |
 
 :::info
 In the version numbers above, the `.z` indicates the latest available patch version for that minor release.
@@ -37,9 +37,10 @@ If your GitLab version is lower than `17.8.5`, please refer to the [GitLab Data
 :::warning
 To safely upgrade your GitLab version to a new version, please note the following:
 
-1. Before upgrading the GitLab instance, please complete the data backup of the instance.
-2. Upgrading GitLab takes some time, depending on the GitLab data size and the version gap between the current version and target version (number of upgrades)
-3. The instance will be unavailable during the upgrade process.
+1. **PostgreSQL Version Check**: [Ensure your PostgreSQL version meets the requirements for your target GitLab version](../install/02_gitlab_credential.mdx#pg-requirements)
+2. Before upgrading the GitLab instance, please complete the data backup of the instance.
+3. Upgrading GitLab takes some time, depending on the GitLab data size and the version gap between the current version and target version (number of upgrades)
+4. The instance will be unavailable during the upgrade process.
 :::
 
 When upgrading, you need to upgrade the <ExternalSiteLink name="acp" href="extend/operator.html#upgrading-operators" children="Operator" /> version and instance version in sequence according to the upgrade path. Upgrading the Operator will not automatically upgrade the instance version, and the upgraded Operator will not manage old GitLab instances, so you need to manually trigger the instance upgrade in time.