diff --git a/doc/update/background_migrations.md b/doc/update/background_migrations.md index 73a50c47b92a3ad77af8219bb1bc4f343584b2cd..d0d255d1c75ab92e72f05b2ffbc72f21fd8147c4 100644 --- a/doc/update/background_migrations.md +++ b/doc/update/background_migrations.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed > - Batched background migrations [introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/51332) in GitLab 13.11 [with a flag](../user/feature_flags.md) named `execute_batched_migrations_on_schedule`. Disabled by default. > - Feature flag `execute_batched_migrations_on_schedule` [enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/329511) in GitLab 13.12. diff --git a/doc/update/background_migrations_troubleshooting.md b/doc/update/background_migrations_troubleshooting.md index 45d61119a233aee4f97c1fa090194a27f1e8ebba..60b89686801417f83b8d7922e62514518626ab7f 100644 --- a/doc/update/background_migrations_troubleshooting.md +++ b/doc/update/background_migrations_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed <!-- Linked from lib/gitlab/database/migrations/batched_background_migration_helpers.rb --> diff --git a/doc/update/index.md b/doc/update/index.md index dbb29f6cb6f2f419707dbd7937cc2fdd503f4e0f..89a6507411ca456327d9b578aa5d906291eeb986 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -9,7 +9,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Upgrading GitLab is a relatively straightforward process, but the complexity can increase based on the installation method you have used, how old your @@ -123,7 +123,7 @@ To address the above two scenarios, it is advised to do the following prior to u DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This section is only applicable if you have enabled the [Elasticsearch integration](../integration/advanced_search/elasticsearch.md). Major releases require all [advanced search migrations](../integration/advanced_search/elasticsearch.md#advanced-search-migrations) diff --git a/doc/update/package/convert_to_ee.md b/doc/update/package/convert_to_ee.md index adb5d0535241eba11eb76c81b14f2c7958e4e352..437cfaa19edb24a31de960b9e452684a0cce337b 100644 --- a/doc/update/package/convert_to_ee.md +++ b/doc/update/package/convert_to_ee.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed To convert an existing GitLab Community Edition (CE) server installed using the Omnibus GitLab packages to GitLab [Enterprise Edition](https://about.gitlab.com/pricing/) (EE), you install the EE diff --git a/doc/update/package/downgrade.md b/doc/update/package/downgrade.md index eff85ac9709763e675401b6fd02eb89f090903fb..40e86020b2426d6ce50042ef8190f8053013392d 100644 --- a/doc/update/package/downgrade.md +++ b/doc/update/package/downgrade.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This section contains general information on how to revert to an earlier version of a package. diff --git a/doc/update/package/index.md b/doc/update/package/index.md index 9994c17a87dcace2e05d2382e7f8f444588390b9..9d97450e0c4956a56c1534c58330a99bffa096e7 100644 --- a/doc/update/package/index.md +++ b/doc/update/package/index.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed You can upgrade GitLab to a new version by using the GitLab package. diff --git a/doc/update/package/package_troubleshooting.md b/doc/update/package/package_troubleshooting.md index 1a1ee330ea2584bea1ef8b59ce2c994530aa35c7..aa24d7823a2d04486c05b5265e8e59f95c9866b6 100644 --- a/doc/update/package/package_troubleshooting.md +++ b/doc/update/package/package_troubleshooting.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Get the status of a GitLab installation diff --git a/doc/update/patch_versions.md b/doc/update/patch_versions.md index 767511e9720bca65b26e31016fe1121b0cf4fa66..72ab4bd30fe0b48073850e10b4c51a405e238d8c 100644 --- a/doc/update/patch_versions.md +++ b/doc/update/patch_versions.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed ## Select Version to Install @@ -107,7 +107,7 @@ sudo -u git -H make DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow the [install instruction](../integration/advanced_search/elasticsearch.md#install-elasticsearch). diff --git a/doc/update/plan_your_upgrade.md b/doc/update/plan_your_upgrade.md index a48532da4ac53a28a1dda831c0202400aca0753b..2a971c8ca0d5b2360658d15d81ccd6157dd52c87 100644 --- a/doc/update/plan_your_upgrade.md +++ b/doc/update/plan_your_upgrade.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This document serves as a guide to create a strong plan to upgrade a self-managed GitLab instance. diff --git a/doc/update/upgrading_from_ce_to_ee.md b/doc/update/upgrading_from_ce_to_ee.md index fe248c05d54340d28c0366d0575b7127c9b22def..e7cdb5de9c701b44a0c2d75b3dd4b5a5c9af66bd 100644 --- a/doc/update/upgrading_from_ce_to_ee.md +++ b/doc/update/upgrading_from_ce_to_ee.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed NOTE: In the past we used separate documents for upgrading from @@ -86,7 +86,7 @@ sudo -u git -H bundle exec rake cache:clear RAILS_ENV=production DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow the [install instruction](../integration/advanced_search/elasticsearch.md#install-elasticsearch). diff --git a/doc/update/upgrading_from_source.md b/doc/update/upgrading_from_source.md index c8df168493eed21b222aa13c96eb97c745886f84..51d2f88d0ba9ca549c60b61bc2c88fd6eb4ab6ba 100644 --- a/doc/update/upgrading_from_source.md +++ b/doc/update/upgrading_from_source.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Make sure you view this upgrade guide from the branch (version) of GitLab you would like to install (for example, `16.0`). You can select the required version of documentation in the dropdown list in the upper-right corner of GitLab documentation page. diff --git a/doc/update/versions/gitlab_14_changes.md b/doc/update/versions/gitlab_14_changes.md index 07434ce85f9ecc1e006704a74010fddfbf67b046..b7c304f2ba2011c247ffc34eef991906362252d2 100644 --- a/doc/update/versions/gitlab_14_changes.md +++ b/doc/update/versions/gitlab_14_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 14. Ensure you review these instructions for: @@ -118,7 +118,7 @@ For more information about upgrading GitLab Helm Chart, see [the release notes f DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - **Do not** upgrade to GitLab 14.9.0. Instead, use 14.9.1 or later. @@ -215,7 +215,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - LFS objects import and mirror issue in GitLab 14.6.0 to 14.7.2. When Geo is enabled, LFS objects fail to be saved for imported or mirrored projects. @@ -241,7 +241,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - LFS objects import and mirror issue in GitLab 14.6.0 to 14.7.2. When Geo is enabled, LFS objects fail to be saved for imported or mirrored projects. @@ -329,7 +329,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -358,7 +358,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.4.0 through 14.4.2](#1440) that can affect Geo and other features that rely on cronjobs. We recommend upgrading to GitLab 14.4.3 or later. @@ -413,7 +413,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -584,7 +584,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -689,7 +689,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - There is [an issue in GitLab 14.2 through 14.7](https://gitlab.com/gitlab-org/gitlab/-/issues/299819#note_822629467) that affects Geo when the GitLab-managed object storage replication is used, causing blob object types to fail synchronization. @@ -772,7 +772,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We found an [issue](https://gitlab.com/gitlab-org/gitlab/-/issues/336013) where the container registry replication wasn't fully working if you used multi-arch images. In case of a multi-arch image, only the primary architecture @@ -933,7 +933,7 @@ Other issues: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We found an issue where [Primary sites cannot be removed from the UI](https://gitlab.com/gitlab-org/gitlab/-/issues/338231). diff --git a/doc/update/versions/gitlab_15_changes.md b/doc/update/versions/gitlab_15_changes.md index 94295365db048428707e7c65aad7d313620b6282..564b1d7c988ee2a3b212a6b4bf3319a17ff182ac 100644 --- a/doc/update/versions/gitlab_15_changes.md +++ b/doc/update/versions/gitlab_15_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 15. Ensure you review these instructions for: @@ -44,7 +44,7 @@ see [Packaged PostgreSQL deployed in an HA/Geo Cluster](https://docs.gitlab.com/ DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - Some project imports do not initialize wiki repositories on project creation. See [the details and workaround](gitlab_16_changes.md#wiki-repositories-not-initialized-on-project-creation). @@ -144,7 +144,7 @@ if you can't upgrade to 15.11.12 and later. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -194,7 +194,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -206,7 +206,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -220,7 +220,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -235,7 +235,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -252,7 +252,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -266,7 +266,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -280,7 +280,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -294,7 +294,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -308,7 +308,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the upgrades. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -323,7 +323,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -385,7 +385,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -402,7 +402,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. - Affected versions: GitLab versions 15.6.x, 15.7.x, and 15.8.0 - 15.8.2. @@ -416,7 +416,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -429,7 +429,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -443,7 +443,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6, and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -457,7 +457,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -471,7 +471,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -485,7 +485,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Container registry push events are rejected](https://gitlab.com/gitlab-org/gitlab/-/issues/386389) by the `/api/v4/container_registry_event/events` endpoint resulting in Geo secondary sites not being aware of updates to container registry images and subsequently not replicating the updates. Secondary sites may contain out of date container images after a failover as a consequence. This affects versions 15.6.0 - 15.6.6 and 15.7.0 - 15.7.2. If you're using Geo with container repositories, you are advised to upgrade to GitLab 15.6.7, 15.7.3, or 15.8.0 which contain a fix for this issue and avoid potential data loss after a failover. - We discovered an issue where [replication and verification of projects and wikis was not keeping up](https://gitlab.com/gitlab-org/gitlab/-/issues/387980) on small number of Geo installations. Your installation may be affected if you see some projects and/or wikis persistently in the "Queued" state for verification. This can lead to data loss after a failover. @@ -524,7 +524,7 @@ potentially cause downtime. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -595,7 +595,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -674,7 +674,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -749,7 +749,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -826,7 +826,7 @@ A [license caching issue](https://gitlab.com/gitlab-org/gitlab/-/issues/376706) DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - `pg_upgrade` fails to upgrade the bundled PostregSQL database to version 13. See [the details and workaround](#pg_upgrade-fails-to-upgrade-the-bundled-postregsql-database-to-version-13). @@ -870,7 +870,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - [Geo proxying](../../administration/geo/secondary_proxy/index.md) was [enabled by default for different URLs](https://gitlab.com/gitlab-org/gitlab/-/issues/346112) in 15.1. This may be a breaking change. If needed, you may [disable Geo proxying](../../administration/geo/secondary_proxy/index.md#disable-geo-proxying). If you are using SAML with different URLs, you must modify your SAML configuration and your Identity Provider configuration. For more information, see the [Geo with Single Sign-On (SSO) documentation](../../administration/geo/replication/single_sign_on.md). - LFS transfers can redirect to the primary from secondary site mid-session. See @@ -1053,7 +1053,7 @@ DETAILS: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed - Incorrect object storage LFS files deletion on Geo secondary sites. See [the details and workaround](#incorrect-object-storage-lfs-file-deletion-on-secondary-sites). diff --git a/doc/update/versions/gitlab_16_changes.md b/doc/update/versions/gitlab_16_changes.md index 58411f6d4eec8aa3699f302882062e25872d03f2..680858ba36f4de096338b63238ca39d15631b640 100644 --- a/doc/update/versions/gitlab_16_changes.md +++ b/doc/update/versions/gitlab_16_changes.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed This page contains upgrade information for minor and patch versions of GitLab 16. Ensure you review these instructions for: @@ -702,7 +702,7 @@ Workaround: A possible workaround is to [disable proxying](../../administration/ DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Specific information applies to installations using Geo: @@ -784,7 +784,7 @@ Specific information applies to Linux package installations: DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Specific information applies to installations using Geo: diff --git a/doc/update/with_downtime.md b/doc/update/with_downtime.md index 8e29097224600d3ab037986b9ccadd78ab4c05ad..7d4a216050f9ca6c9decc1778029170eeb62aa11 100644 --- a/doc/update/with_downtime.md +++ b/doc/update/with_downtime.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed While you can upgrade a multi-node GitLab deployment [with zero downtime](zero_downtime.md), there are a number of constraints. In particular, you can upgrade to only one minor release @@ -197,7 +197,7 @@ Upgrade a standalone Redis server by [upgrading the GitLab package](package/inde DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Follow [the zero downtime instructions](zero_downtime.md#redis-ha-using-sentinel) for upgrading your Redis HA cluster. diff --git a/doc/update/zero_downtime.md b/doc/update/zero_downtime.md index 7a9d726cc903694c0eb92f6789eab8152d898d21..c33b78cd1c433ff9e80dc6b88568cc1f57050049 100644 --- a/doc/update/zero_downtime.md +++ b/doc/update/zero_downtime.md @@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w DETAILS: **Tier:** Free, Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed It's possible to upgrade to a newer major, minor, or patch version of GitLab without having to take your GitLab instance offline. However, for this to work @@ -333,7 +333,7 @@ setting `gitlab_rails['auto_migrate'] = false` in DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed Package upgrades may involve version updates to the bundled Redis service. On instances using [Redis for scaling](../administration/redis/index.md), @@ -436,7 +436,7 @@ procedure. DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: You can only upgrade one minor release at a time. @@ -557,7 +557,7 @@ setting `gitlab_rails['auto_migrate'] = false` in DETAILS: **Tier:** Premium, Ultimate -**Offering:** Self-managed, GitLab Dedicated +**Offering:** Self-managed WARNING: You can only upgrade one minor release at a time. You also must first start with the Gitaly cluster, updating Gitaly one node one at a time. This will ensure access to the Git repositories for the remainder of the upgrade process.