diff --git a/doc/update/index.md b/doc/update/index.md
index 89a6507411ca456327d9b578aa5d906291eeb986..ae6fd66d3da203224a6863fb6c050a136a01b70d 100644
--- a/doc/update/index.md
+++ b/doc/update/index.md
@@ -305,6 +305,10 @@ NOTE:
 Specific information that follow related to Ruby and Git versions do not apply to [Omnibus installations](https://docs.gitlab.com/omnibus/)
 and [Helm Chart deployments](https://docs.gitlab.com/charts/). They come with appropriate Ruby and Git versions and are not using system binaries for Ruby and Git. There is no need to install Ruby or Git when utilizing these two approaches.
 
+### GitLab 17
+
+Before upgrading to GitLab 17, see [GitLab 17 changes](versions/gitlab_17_changes.md).
+
 ### GitLab 16
 
 Before upgrading to GitLab 16, see [GitLab 16 changes](versions/gitlab_16_changes.md).
diff --git a/doc/update/versions/gitlab_17_changes.md b/doc/update/versions/gitlab_17_changes.md
new file mode 100644
index 0000000000000000000000000000000000000000..09b3d7d44e5f89e6067821378980675356a360af
--- /dev/null
+++ b/doc/update/versions/gitlab_17_changes.md
@@ -0,0 +1,27 @@
+---
+stage: Systems
+group: Distribution
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+---
+
+# GitLab 17 changes
+
+DETAILS:
+**Tier:** Free, Premium, Ultimate
+**Offering:** Self-managed
+
+This page contains upgrade information for minor and patch versions of GitLab 17.
+Ensure you review these instructions for:
+
+- Your installation type.
+- All versions between your current version and your target version.
+
+For more information about upgrading GitLab Helm Chart, see [the release notes for 7.0](https://docs.gitlab.com/charts/releases/7_0.html).
+
+## 17.0.0
+
+- You should [migrate to the new runner registration workflow](../../ci/runners/new_creation_workflow.md) before upgrading to GitLab 17.0.
+
+  In GitLab 16.0, we introduced a new runner creation workflow that uses runner authentication tokens to register runners.
+  The legacy workflow that uses registration tokens is now disabled by default in GitLab 17.0 and will be removed in GitLab 18.0.
+  If registration tokens are still being used, upgrading to GitLab 17.0 will cause runner registration to fail.