From cf4769c89dbb63371a3388bbfe86d77d9bb612a9 Mon Sep 17 00:00:00 2001 From: Emily Chang <echang@gitlab.com> Date: Fri, 10 Nov 2023 05:35:17 +0000 Subject: [PATCH] Add breaking change for azure storage --- doc/update/versions/gitlab_16_changes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/update/versions/gitlab_16_changes.md b/doc/update/versions/gitlab_16_changes.md index 295acb9c2dd9c..836f5d188c594 100644 --- a/doc/update/versions/gitlab_16_changes.md +++ b/doc/update/versions/gitlab_16_changes.md @@ -471,6 +471,7 @@ by this issue. [throw errors on startup](../../install/docker.md#threaderror-cant-create-thread-operation-not-permitted). - Starting with 16.0, GitLab self-managed installations now have two database connections by default, instead of one. This change doubles the number of PostgreSQL connections. It makes self-managed versions of GitLab behave similarly to GitLab.com, and is a step toward enabling a separate database for CI features for self-managed versions of GitLab. Before upgrading to 16.0, determine if you need to [increase max connections for PostgreSQL](https://docs.gitlab.com/omnibus/settings/database.html#configuring-multiple-database-connections). - This change applies to installation methods with Linux packages (Omnibus), GitLab Helm chart, GitLab Operator, GitLab Docker images, and self-compiled installations. +- Container registry using Azure storage might be empty with zero tags. You can fix this by following the [breaking change instructions](../deprecations.md#azure-storage-driver-defaults-to-the-correct-root-prefix). ### Linux package installations -- GitLab