Sourcegraph self-hosted on Kubernetes upgrade notes

This page lists the changes that are relevant for upgrading Sourcegraph on Kubernetes with Kustomize and Helm.

For upgrade procedures or general info about sourcegraph versioning see the links below:

• Kubernetes Kustomize upgrade procedures
• Kubernetes Helm upgrade procedures
• General upgrade info
• Technical changelog

Attention: These notes may contain relevant information about the infrastructure update such as resource requirement changes or versions of dependencies (Docker, Kubernetes, externalized databases).

If the notes indicate a patch release exists, target the highest one.

7.1.0

• The bundled Jaeger instance has been upgraded from v1 to v2.16.0. Jaeger v2 replaces all legacy CLI flags with an OpenTelemetry Collector-style YAML configuration file. Helm users: the jaeger.args value now defaults to ["--config=/etc/jaeger/jaeger-config.yaml"] and common settings are exposed through jaeger.config (e.g. jaeger.config.maxTraces, jaeger.config.logLevel, jaeger.config.samplingDefaultProbability). Any custom CLI flags previously passed via jaeger.args must be migrated to the YAML config format. For full control, set jaeger.config.existingConfigMap to the name of your own ConfigMap. See the Kubernetes deployment docs for available configuration options.

6.10.0

• Port names have been updated on services and pods, to unblock Kubernetes service meshes from auto-configuring themselves for the traffic type, since most inter-pod communication has been switched from http to gRPC [PR 756]. If you are using Istio (or similar service meshes), and our Envoy filter example, and your pods fail to communicate after upgrading to >= v6.10, please remove the Envoy filter and try again so your service mesh can auto-configure itself based on the new port names.

6.4.0

• The repo-updater service is no longer needed and will be removed from deployment methods going forward.
• The symbols service and searcher service have been merged and symbols will be removed from deployment methods going forward. Consider moving env vars set on symbols to the searcher deployment before upgrading and reallocating resources from symbols to searcher.

6.2.2553

Known issues

Customers running Sourcegraph versions prior to v6.2.2553 and using the Sourcegraph provided PostgreSQL containers may encounter PostgreSQL collation version mismatch warnings after upgrading to more recent Sourcegraph versions due to an underlying glibc version update.

When logging into the database via psql or similar tools you may see the following warning:

Warning: database "sg" has a collation version mismatch DETAIL: The database was created using collation version 2.40, but the operating system provides version 2.41.

Mismatched collation versions can lead to database index corruption if left unchecked.

Affected services

• pgsql container
• codeintel-db container
• codeinsights-db container

Only self-hosted customers using the Sourcegraph provided PostgreSQL container images are affected.

Self-hosted customers using external databases, such as AWS RDS, GCP CloudSQL, or another self-managed solution are NOT affected.

See our PostgreSQL collation version mismatch resolution notes for more details.

6.0.0

• Sourcegraph 6.0.0 no longer supports PostgreSQL 12, admins must upgrade to PostgreSQL 16. See our postgres 12 end of life notice! As well as supporting documentation and advisements on how to upgrade.

Warning: The Kubernetes Helm deployment type does not support MVU from Sourcegraph v5.9.45 versions and earlier to Sourcegraph v6.0.0. Admins seeking to upgrade to Sourcegraph v6.0.0 should upgrade to v5.11.6271 then use the standard upgrade procedure to get to v6.0.0. This is because migrator v6.0.0 will no longer connect to Postgres 12 databases. For more info see our PostgreSQL upgrade docs.

5.10.1164

• This release resolves an issue in the v5.10.0 release which prevented multiversion upgrades from working. You may now target v5.10.1164 using migrator's upgrade command.

Note: For versions prior to 6.12.0, you could also use autoupgrade by setting the environment variable SRC_AUTOUPGRADE_IGNORE_DRIFT=true on the frontend deployment. Autoupgrade has been removed in Sourcegraph 6.12.0 and later.

5.10.0

Warning: Admins are advised to upgrade directly to v5.10.1164 circumventing this release.

Warning: This release updates the database container images from Postgres 12 to Postgres 16, and begins using Wolfi based images. Customers are advised to take a database backup before upgrading! See our postgres 12 end of life notice!

Warning: automatic and migrator upgrade command will not work for this release, please upgrade directly to v5.10.1164, or to a 5.9 version and conduct a standard upgrade using migrator's default up command!

Notes:

• The container image for pgsql and codeintel-db have been renamed from postgres-12-alpine and codeintel-db respectively to postgresql-16. The codeinsights-db container has been renamed to postgresql-16-codeinsights.
• Admins using external dbs who have not yet upgraded from postgres 12 to postgres 16, can expect to see database drift after upgrading to 5.10.0. The new expected schema definition for Sourcegraph is based on postgres 16. The schema drift is the result of automatic changes made to the schema by pg_upgrade utils, and will not cause issues in the application.
  • Admins should not run migrators suggested drift fixes, and should instead upgrade their database from postgres 12 to postgres 16.
• Postgres 12 image containers cannot be started with data volumes which have been upgraded by postgres 16.

5.2.0

Notes:

• The GitHub proxy service has been removed and is no longer required. You can safely remove it.

5.1.7

Notes:

• v5.1.7 of the deploy-sourcegraph-helm repo was initially released with the precise-code-intel worker service unable to write to /tmp. The release was overwritten, users who have not yet upgraded will be unaffected. Users who have already upgraded may ammend this issue by pulling in the fix with helm repo update and rerunning helm upgrade.

5.1.5

Notes:

• Upgrades from versions v5.0.3, v5.0.4, v5.0.5, and v5.0.6 to v5.1.5 are affected by an ordering error in the frontend databases migration tree.