From dba4b4eafc2b04344e8f26c7954a4af255cd3708 Mon Sep 17 00:00:00 2001
From: Albert Salim <asalim@gitlab.com>
Date: Mon, 26 Feb 2024 15:33:27 +0000
Subject: [PATCH] Document issue - Google Cloud Secret Manager with SaaS Runner

---
 doc/ci/secrets/gcp_secret_manager.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/ci/secrets/gcp_secret_manager.md b/doc/ci/secrets/gcp_secret_manager.md
index a5ebc3e685471..cc9084ea0aa57 100644
--- a/doc/ci/secrets/gcp_secret_manager.md
+++ b/doc/ci/secrets/gcp_secret_manager.md
@@ -128,3 +128,12 @@ Either modify your attribute mapping or the incoming assertion to produce a mapp
 
 For example, for a `gitlab-org/gitlab` branch, the payload would be `project_path:gitlab-org/gitlab:ref_type:branch:ref:{branch_name}`,
 so the branch name should be 76 characters or less.
+
+### `WARNING: Not resolved: no resolver that can handle the secret` warning
+
+The Google Cloud Secret Manager integration requires at least GitLab 16.8 and GitLab Runner 16.8.
+This warning appears if the job is executed by a runner using a version earlier than 16.8.
+
+On GitLab.com, there is a [known issue](https://gitlab.com/gitlab-org/ci-cd/shared-runners/infrastructure/-/issues/176)
+causing SaaS runners to run an older version. As a workaround until this issue is fixed,
+you can register your own GitLab Runner with version 16.8 or later.
-- 
GitLab