Skip to content

fix/docs: Clarify Postgres upgrade requirements for Helm #1629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marcleblanc2 wants to merge 6 commits into
base: main
Choose a base branch
from
Open

fix/docs: Clarify Postgres upgrade requirements for Helm #1629

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
38d24a2
fix/docs: Clarify Postgres upgrade requirements for Helm
marcleblanc2 Feb 20, 2026
3cf9d6d
Further clarity
marcleblanc2 Feb 20, 2026
2b78421
Fix markdown spacing for Vercel
marcleblanc2 Feb 20, 2026
583f5b2
Fix formatting
marcleblanc2 Feb 20, 2026
b4dd00b
Updating for sourcegraph-migrator Helm chart missing k8s secret update
marcleblanc2 Feb 20, 2026
2737d13
Reformat for easier step following
marcleblanc2 Feb 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 26 additions & 24 deletions docs/self-hosted/deploy/kubernetes/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Contributor

@DaedalusG DaedalusG Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be minor or major -- users on 6.12.0 will be able to standard upgrade to 7.0.0

Copy link
Contributor Author

@marcleblanc2 marcleblanc2 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know, but haven't found a less confusing way to phrase it.

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.

<Callout type="warning">
You can only upgrade one minor version of Sourcegraph at a time.
Copy link
Contributor

@DaedalusG DaedalusG Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why remove this callout? Its true that for standard upgrades you can only go across a minor version

Copy link
Contributor Author

@marcleblanc2 marcleblanc2 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's duplicative of the previous callout.

</Callout>

**Step 2:** Update your copy of the Sourcegraph Helm repo to ensure you have all the latest versions:

```sh
Expand All @@ -1001,11 +997,32 @@ When all pods have restarted and show as Running, you can browse to your Sourceg

### Multi-version upgrades

<Callout type="info">

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)

</Callout>

<Callout type="warning">
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.

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 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:

- Deploy a v6 version of either the `sourcegraph` or `sourcegraph-migrator` Helm chart
Copy link
Contributor

@DaedalusG DaedalusG Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version 6.0.0 and greater migrators will refuse to connect to a PG12 db. I'm not relying on the migrator job to bring up the dbs and crashloop attempts to connect to them until they complete their PG upgrade will work 🤔

Copy link
Contributor Author

@marcleblanc2 marcleblanc2 Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added the database-maintenance-override.yaml example override file to the Helm repo, so customers can use their regular Helm chart and override file, to let the database pods come up on their own to run the upgrade without any other pods trying to connect to them.

Optionally, the override can be used to operate the migrator init container in the frontend pod.

I think the sourcegraph-migrator helm chart should work fine, but I'll test it before merging this.

- 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

For details, see our [PostgreSQL upgrade docs](/self-hosted/postgres#requirements)

</Callout>

### Multi-version upgrade procedure
Expand All @@ -1017,21 +1034,6 @@ When all pods have restarted and show as Running, you can browse to your Sourceg

**Step 2:**

<Callout type="warning">

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).

</Callout>

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:

Expand Down