Cut 1.20.4 release

[davidnuzik]

Upstream: kubernetes/sig-release#1467 kubernetes/sig-release#1470

Notice:
Upstream plans to get patch releases out by 2/17/2021.
v1.17 has reached end of life upstream. We follow what upstream does with releases, and v1.17 will not be included in this month's patch releases as there is nothing to release from upstream.

Summary:
Task covering patch release work.
Dev Complete: 2/12/2021

List of required releases:
To release as soon as able for QA:

• v1.20.34-rc1+k3s1

To release once have approval from QA:

• v1.20.34+k3s1

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: Prep PR for rancher/kontainer-driver-metadata (bump all the patch versions as necessary)
• 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. We will make a special exception this round with 1.20.34 and QA will focus to get higher priority issues closed out and test others post-release.

Vendor and release work:

• Release Captain: Vendor in the new patch version and release rancher/kubernetes
• Release Captain KDM Work: Merge PR for rancher/kontainer-driver-metadata into the dev branches
• Release Captain: Tag and release any necessary RCs for QA to test K3s and KDM on the Rancher side
• Release Captain: Tag and release when have QA approval
• PM: Create an issue to mark the latest release as stable (this is done typically not later than 1 days post release patch release, 7 days post new minor release) Mark 1.20.4+k3s1 as stable #2858

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.
• PM: Close the milestone in GitHub. (Special case -- to be done post-release, at a later time)

[davidnuzik]

Closing. QA is testing a few remaining issues in the milestone. I will close the milestone later. This is a special case; we would not normally leave the milestone open but these are low priority issues.