diff --git a/.gitlab/CODEOWNERS b/.gitlab/CODEOWNERS
index cba37fd79dee188940a611a3437f76bcc1ecc1ac..e9f18df4b4afae2af208e603dd9916bb83d7a036 100644
--- a/.gitlab/CODEOWNERS
+++ b/.gitlab/CODEOWNERS
@@ -158,6 +158,9 @@ Dangerfile
 ^[Distribution] @gitlab-org/distribution
 /lib/support/
 
+[Upgrade path] @gitlab-org/distribution
+/config/upgrade_path.yml
+
 # Secure & Threat Management ownership delineation
 # https://about.gitlab.com/handbook/engineering/development/threat-management/delineate-secure-threat-management.html#technical-boundaries
 ^[Threat Insights backend] @gitlab-org/govern/threat-insights-backend-team
diff --git a/config/upgrade_path.yml b/config/upgrade_path.yml
new file mode 100644
index 0000000000000000000000000000000000000000..2b81493f14f55b91db4eade1bc0e927ca141a3aa
--- /dev/null
+++ b/config/upgrade_path.yml
@@ -0,0 +1,72 @@
+---
+- major: 8
+  minor: 11
+
+- major: 8
+  minor: 12
+
+- major: 8
+  minor: 17
+
+- major: 9
+  minor: 5
+
+- major: 10
+  minor: 8
+
+- major: 11
+  minor: 11
+
+- major: 12
+  minor: 0
+
+- major: 12
+  minor: 1
+
+- major: 12
+  minor: 10
+
+- major: 13
+  minor: 0
+
+- major: 13
+  minor: 1
+
+- major: 13
+  minor: 8
+
+- major: 13
+  minor: 12
+
+- major: 14
+  minor: 0
+  comments: "**Migrations can take a long time!**"
+
+- major: 14
+  minor: 3
+  comments: "See [GitLab Issue #354211](https://gitlab.com/gitlab-org/gitlab/-/issues/354211#note_962223568)"
+
+- major: 14
+  minor: 9
+  comments: "See [GitLab Issue #354211](https://gitlab.com/gitlab-org/gitlab/-/issues/354211#note_962223568)"
+
+- major: 14
+  minor: 10
+
+- major: 15
+  minor: 0
+
+- major: 15
+  minor: 4
+
+- major: 15
+  minor: 11
+
+- major: 16
+  minor: 3
+
+- major: 16
+  minor: 7
+
+- major: 16
+  minor: 11
diff --git a/doc/development/avoiding_required_stops.md b/doc/development/avoiding_required_stops.md
index 05ae3efee1e49a112dfa2d03b1b4a4463a2b2a74..68b510615818a18a456de27ccaf6468e7c80cad4 100644
--- a/doc/development/avoiding_required_stops.md
+++ b/doc/development/avoiding_required_stops.md
@@ -157,12 +157,10 @@ Slack channel.
 Before releasing a known required stop, complete these steps. If the required stop
 is identified after release, the following steps must still be completed:
 
-1. Update [upgrade paths](../update/index.md#upgrade-paths) documentation to include the new
-   required stop.
+1. In the same MR, update the [upgrade paths](../update/index.md#upgrade-paths) documentation to include the new
+   required stop, and the [`upgrade_path.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/upgrade_path.yml).
+   The `upgrade_path.yml` is the single source of truth (SSoT) for all our required stops.
 1. Communicate the changes with the customer Support and Release management teams.
-1. Update the [`upgrade-path.yml`](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path/-/blob/main/upgrade-path.yml).
-   GitLab Release Tools uses this file to update Omnibus GitLab with the required stop, as well as to feed the
-   the Upgrade Path tool.
 1. If the required stops is database related, file an issue with the Database group to
    squash migrations to that version in the next release. Use this template for your issue:
 
@@ -187,6 +185,18 @@ is identified after release, the following steps must still be completed:
    [upgrade check hook](https://gitlab.com/gitlab-org/charts/gitlab/-/blame/master/templates/_runcheck.tpl#L32)
    to the required stop version.
 
+## GitLab-maintained projects which depend on `upgrade_path.yml`
+
+We have multiple projects depending on the `upgrade_path.yml` SSoT. Therefore,
+any change to the structure of this file needs to take into consideration that
+it might affect one of the following projects:
+
+- [Release Tools](https://gitlab.com/gitlab-org/release-tools)
+- [Support Upgrade Path](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path)
+- [Upgrade Tester](https://gitlab.com/gitlab-org/quality/upgrade-tester)
+- [GitLab QA](https://gitlab.com/gitlab-org/gitlab-qa)
+- [PostgreSQL Dump Generator](https://gitlab.com/gitlab-org/quality/pg-dump-generator)
+
 ## Further reading
 
 - [Documentation: Database required stops](database/required_stops.md)
@@ -198,4 +208,5 @@ is identified after release, the following steps must still be completed:
 - [Issue: Put in place measures to avoid addition/proliferation of GitLab upgrade path stops](https://gitlab.com/gitlab-org/gitlab/-/issues/375553)
 - [Issue: Brainstorm ways for background migrations to be finalized without introducing a required upgrade step](https://gitlab.com/gitlab-org/gitlab/-/issues/357561)
 - [Issue: Scheduled required paths for GitLab upgrades to improve UX](https://gitlab.com/gitlab-org/gitlab/-/issues/358417)
+- [Issue: Automate upgrade stop planning process](https://gitlab.com/gitlab-org/gitlab/-/issues/438921)
 - [Epic: GitLab Releases and Maintenance policies](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/988)
diff --git a/spec/config/upgrade_path_spec.rb b/spec/config/upgrade_path_spec.rb
new file mode 100644
index 0000000000000000000000000000000000000000..6f56a25aeca69adc50acdececd76d0e30315763a
--- /dev/null
+++ b/spec/config/upgrade_path_spec.rb
@@ -0,0 +1,13 @@
+# frozen_string_literal: true
+
+require 'spec_helper'
+
+RSpec.describe 'UpgradePath', feature_category: :shared do
+  it 'is parsed correctly' do
+    upgrade_path = YAML.safe_load_file(Rails.root.join('config/upgrade_path.yml'))
+
+    expect(upgrade_path.first).to eq({ "major" => 8, "minor" => 11 })
+    expect(upgrade_path[13]).to eq({ "major" => 14, "minor" => 0,
+"comments" => "**Migrations can take a long time!**" })
+  end
+end