From 38d24a2137240d57fad8dc38eb2881d7206064fd Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 14:41:43 -0700 Subject: [PATCH 1/6] fix/docs: Clarify Postgres upgrade requirements for Helm --- docs/self-hosted/deploy/kubernetes/index.mdx | 23 +++++++------------- 1 file changed, 8 insertions(+), 15 deletions(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index d92af9231..e8430dd8f 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -969,14 +969,10 @@ The following procedures describe the process to update a Helm Sourcegraph insta ### Standard upgrades -A [standard upgrade](/self-hosted/updates/#upgrade-types) occurs between a Sourcegraph version and the minor or major version released immediately after it. If you would like to jump forward several versions, you must perform a [multi-version upgrade](#multi-version-upgrades) instead. +A [standard upgrade](/self-hosted/updates/#upgrade-types) occurs between your current Sourcegraph version and the next minor version released immediately after it. If you would like to jump forward several versions, you must perform a [multi-version upgrade](#multi-version-upgrades) instead. **Step 1:** Review [Helm Changelog] and [Sourcegraph Changelog] and select the most recent version compatible with your current Sourcegraph version. - - You can only upgrade one minor version of Sourcegraph at a time. - - **Step 2:** Update your copy of the Sourcegraph Helm repo to ensure you have all the latest versions: ```sh @@ -1019,16 +1015,13 @@ When all pods have restarted and show as Running, you can browse to your Sourceg - The Kubernetes Helm deployment type does not support MVU from Sourcegraph - `v5.9.45` versions and earlier to ANY version `v6.0.x` or later. Admins - seeking to upgrade to any Sourcegraph version `v6.0.x` or later (including - `v6.1.x`, `v6.2.x`, etc.) must first upgrade to `v5.10.3940` or - `v5.11.6271` and then use the standard upgrade procedure to get to their - target version. This is because migrator in all versions from `v6.0.0` - onwards will no longer connect to Postgres 12 databases. Additionally, - starting in Sourcegraph 7.0.0, the automatic PostgreSQL 12 to 16 upgrade - entrypoint script has been removed entirely. For more info see - our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). + - The minimum supported version of Postgres is v16, as of Sourcegraph v6 + - If using external databases, ensure their Postgres version is >= v16 before upgrading to Sourcegraph >= v6 + - If using our default Postgres pods, and upgrading from < v5.10.3940, then prior to upgrading >= v7, you must either: + - Upgrade the 3x Postgres pods to a v6 version, so they can run our Postgres v12 -> v16 upgrade script, which was removed in v7 + - Migrate your databases to an external database management service, using Postgres >= v16 + + For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). From 3cf9d6d5db5817882d187becbd731cd025fd3434 Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 15:15:06 -0700 Subject: [PATCH 2/6] Further clarity --- docs/self-hosted/deploy/kubernetes/index.mdx | 29 +++++++++----------- 1 file changed, 13 insertions(+), 16 deletions(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index e8430dd8f..d2a6a83f6 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -997,11 +997,20 @@ When all pods have restarted and show as Running, you can browse to your Sourceg ### Multi-version upgrades + + Please see our [best practices](/self-hosted/updates/#best-practices) on + upgrades; if you have any concerns about running a multi-version upgrade, + please contact us at + [support@sourcegraph.com](mailto:support@sourcegraph.com). + + - Please see our [cautionary note](/self-hosted/updates/#best-practices) on - upgrades, if you have any concerns about running a multi-version upgrade, - please reach out to us at - [support@sourcegraph.com](mailto:support@sourcegraph.com) for advisement. + - The minimum supported version of Postgres is v16, as of Sourcegraph v6 + - If using external databases, ensure their Postgres version is >= v16 before upgrading to Sourcegraph >= v6 + - If using our default Postgres pods, and upgrading from < v5.10.3940, then prior to upgrading >= v7, you must either: + - Upgrade the 3x Postgres pods to a v6 version, so they can run our Postgres v12 -> v16 upgrade script, which was removed in v7 + - Migrate your databases to an external database management service, using Postgres >= v16 + For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). ### Multi-version upgrade procedure @@ -1013,18 +1022,6 @@ When all pods have restarted and show as Running, you can browse to your Sourceg **Step 2:** - - - - The minimum supported version of Postgres is v16, as of Sourcegraph v6 - - If using external databases, ensure their Postgres version is >= v16 before upgrading to Sourcegraph >= v6 - - If using our default Postgres pods, and upgrading from < v5.10.3940, then prior to upgrading >= v7, you must either: - - Upgrade the 3x Postgres pods to a v6 version, so they can run our Postgres v12 -> v16 upgrade script, which was removed in v7 - - Migrate your databases to an external database management service, using Postgres >= v16 - - For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). - - - Scale down `deployments` and `statefulSets` that access the database, _this step prevents services from accessing the database while schema migrations are in process._ The following services must have their replicas scaled to 0: From 2b78421e069ac3febb3f7eaeee303b83212f22bb Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 15:17:27 -0700 Subject: [PATCH 3/6] Fix markdown spacing for Vercel --- docs/self-hosted/deploy/kubernetes/index.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index d2a6a83f6..7a0c57862 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -998,19 +998,25 @@ When all pods have restarted and show as Running, you can browse to your Sourceg ### Multi-version upgrades + Please see our [best practices](/self-hosted/updates/#best-practices) on upgrades; if you have any concerns about running a multi-version upgrade, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com). + - - The minimum supported version of Postgres is v16, as of Sourcegraph v6 + + The minimum supported version of Postgres is v16, as of Sourcegraph v6 + - If using external databases, ensure their Postgres version is >= v16 before upgrading to Sourcegraph >= v6 - If using our default Postgres pods, and upgrading from < v5.10.3940, then prior to upgrading >= v7, you must either: - Upgrade the 3x Postgres pods to a v6 version, so they can run our Postgres v12 -> v16 upgrade script, which was removed in v7 - Migrate your databases to an external database management service, using Postgres >= v16 + For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). + ### Multi-version upgrade procedure From 583f5b29ef33eb6aaa3c7db74cc8ab7d7017f6df Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 15:39:38 -0700 Subject: [PATCH 4/6] Fix formatting --- docs/self-hosted/deploy/kubernetes/index.mdx | 22 +++++++++++--------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index 7a0c57862..9097fa982 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -999,23 +999,25 @@ When all pods have restarted and show as Running, you can browse to your Sourceg - Please see our [best practices](/self-hosted/updates/#best-practices) on - upgrades; if you have any concerns about running a multi-version upgrade, - please contact us at - [support@sourcegraph.com](mailto:support@sourcegraph.com). + Please see our [best practices](/self-hosted/updates/#best-practices) on upgrades; if you have any concerns about running a multi-version upgrade, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) - The minimum supported version of Postgres is v16, as of Sourcegraph v6 + As of Sourcegraph v6, the minimum supported version of Postgres has been increased from v12 to v16 + + As of Sourcegraph v7, the scripts to upgrade Postgres from v12 to v16 have been removed from our Postgres pods - - If using external databases, ensure their Postgres version is >= v16 before upgrading to Sourcegraph >= v6 - - If using our default Postgres pods, and upgrading from < v5.10.3940, then prior to upgrading >= v7, you must either: - - Upgrade the 3x Postgres pods to a v6 version, so they can run our Postgres v12 -> v16 upgrade script, which was removed in v7 - - Migrate your databases to an external database management service, using Postgres >= v16 + - If using our Postgres pods, and upgrading Sourcegraph from `< v5.10.3940`, then prior to upgrading Sourcegraph to >= v7, you must either: - For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements). + - Upgrade the 3x Postgres pods to a Sourcegraph v6 version, so they can run our Postgres upgrade scripts + + - Or migrate the 3x Postgres databases to an external database management service, using Postgres >= v16 (recommended) + + - If using an external database management service, ensure Postgres is upgraded >= v16 prior to upgrading >= v7 + + For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements) From b4dd00b3871259edc488c189e50b7a252970eea9 Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 16:02:45 -0700 Subject: [PATCH 5/6] Updating for sourcegraph-migrator Helm chart missing k8s secret update --- docs/self-hosted/deploy/kubernetes/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index 9097fa982..8bc33a621 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -1007,15 +1007,15 @@ When all pods have restarted and show as Running, you can browse to your Sourceg As of Sourcegraph v6, the minimum supported version of Postgres has been increased from v12 to v16 - As of Sourcegraph v7, the scripts to upgrade Postgres from v12 to v16 have been removed from our Postgres pods + As of Sourcegraph v7, the scripts to upgrade the Postgres version inside our Postgres pods have been removed - If using our Postgres pods, and upgrading Sourcegraph from `< v5.10.3940`, then prior to upgrading Sourcegraph to >= v7, you must either: - - Upgrade the 3x Postgres pods to a Sourcegraph v6 version, so they can run our Postgres upgrade scripts + - Upgrade the 3x Postgres pods to a Sourcegraph v6 version by deploying a v6 version of either the `sourcegraph` or `sourcegraph-migrator` Helm chart, so the pods can run the Postgres upgrade scripts, then deploying a v7 version of the `sourcegraph` Helm chart to run the migrator MVU - Or migrate the 3x Postgres databases to an external database management service, using Postgres >= v16 (recommended) - - If using an external database management service, ensure Postgres is upgraded >= v16 prior to upgrading >= v7 + - If using an external database management service, ensure Postgres is upgraded >= v16 prior to upgrading Sourcegraph >= v7 For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements) From 2737d133ba4fce78facb825ca2ceb03f20768705 Mon Sep 17 00:00:00 2001 From: Marc <7050295+marcleblanc2@users.noreply.github.com> Date: Fri, 20 Feb 2026 16:13:13 -0700 Subject: [PATCH 6/6] Reformat for easier step following --- docs/self-hosted/deploy/kubernetes/index.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/self-hosted/deploy/kubernetes/index.mdx b/docs/self-hosted/deploy/kubernetes/index.mdx index 8bc33a621..dd2df7591 100644 --- a/docs/self-hosted/deploy/kubernetes/index.mdx +++ b/docs/self-hosted/deploy/kubernetes/index.mdx @@ -1011,9 +1011,13 @@ When all pods have restarted and show as Running, you can browse to your Sourceg - If using our Postgres pods, and upgrading Sourcegraph from `< v5.10.3940`, then prior to upgrading Sourcegraph to >= v7, you must either: - - Upgrade the 3x Postgres pods to a Sourcegraph v6 version by deploying a v6 version of either the `sourcegraph` or `sourcegraph-migrator` Helm chart, so the pods can run the Postgres upgrade scripts, then deploying a v7 version of the `sourcegraph` Helm chart to run the migrator MVU + - Upgrade the 3x Postgres pods to a Sourcegraph v6 version: - - Or migrate the 3x Postgres databases to an external database management service, using Postgres >= v16 (recommended) + - Deploy a v6 version of either the `sourcegraph` or `sourcegraph-migrator` Helm chart + - Watch the 3x Postgres pods' logs, and wait for them to finish running the upgrade scripts + - Deploy a v7 version of the `sourcegraph` Helm chart to run the Migrator MVU + + - Or, migrate the 3x Postgres databases to an external database management service, using Postgres >= v16 (recommended) - If using an external database management service, ensure Postgres is upgraded >= v16 prior to upgrading Sourcegraph >= v7