Cut 1.20.9

[fapatel1]

To release as soon as able for QA:

• v1.20.9-rc1+rke2r1

To release once have approval from QA:

• v1.20.9+rke2r1 (Never release on a Friday unless specified otherwise)

Prep work:

• PM: Dev and QA team to be notified of the incoming releases - send calendar invite
• PM: Dev and QA team to be notified of the date we will mark the latest release as stable - send calendar invite
• QA: Review changes and understand testing efforts
• Release Captain KDM Work: Merge PR for rancher/kontainer-driver-metadata into the dev branches
• Release Captain: Prepare release notes in our private release-notes repo (submit PR for changes taking care to carefully check links and the components, once merged, create the release in GitHub and mark as a draft and check the pre-release box, fill in title, set target release branch, leave tag version blank for now until we are ready to release)
• QA: Validate and close out all issues in the release milestone.

Vendor and release work:

• Release Captain: Tag and release any necessary RCs for QA to test KDM
• Release Captain: Tag and release when have QA approval

Post-Release work:

• Release Captain: Once release is fully complete (CI is all green and all release artifacts exist), edit the release, uncheck "Pre-release", and save.
• Release Captain: Prepare PRs as needed to update KDM in the appropriate dev branches.
• PM: Close the milestone in GitHub.