Goal: 

• 16.2 - Leave the repos hard-coded under the assumption that they do not need to be updated anymore.
• 17.1 - Leave the repos hard-coded under the assumption that only the RHEL 9.2 version will be updated in 2027. We should make sure that we have a Jira tracker to do a one-off update when the transition happens, but I imagine there will be a RelDel task for the transition so we will have artifacts to attach to.

Questions that need to be addressed:

1. How does the repository adjustments module in 16.2 and 17.1 change?
   1. Should the paragraph be preserved, but the list of repos removed in favor of linking to the lifecycle page?
   2. Should the paragraph turn into an admonition that we place anywhere we mention repos in the docs (or perhaps one module in the “planning” section of each guide that mentions repos).

The release notes, upgrade guide, and director guides in 16.2 and 17.1 include the lists of undercloud repositories and overcloud repositories. 

1. How should these lists be maintained going forward? 
2. Do we want to remove these lists and add them to the lifecycle page instead?

Acceptance Criteria:

• Docs updated
• SME review/peer review
• Docs published