Update release notes draft to version v1.34.0-rc.2

[rashansmith]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
This PR updates the Release Notes Draft to k/k v1.34.0-rc.2

Which issue(s) this PR fixes:

Special notes for your reviewer:
This is an automated PR generated from krel The Kubernetes Release Toolbox

[wendy-ha18]

Could we reach out to the author of PR kubernetes/kubernetes#132890 to make sure the PR didn't need release note or the author forgot to include it?
Cause if the PR doesn't need release note, this file can be removed out of maps and release-notes-draft.json/.md file.

[rashansmith]

I reached out. Do we have a limit on when to expect to hear back vs. moving forward.

[wendy-ha18]

Normally when we have time, I would properly suggest to wait for contributor to get back 1 or 2 days cause sometime they will busy with their own schedule. However, considering these factors:

• timing of final release cut today.
• the purpose of PR 132890 was for improving internal test coverage (added a conversion test to check that when a ReplicaSet object is converted to a ReplicationController) only, not end-user visible change as Does my pull request need a release note guidance here.
• this PR is kind cleanup

I would suggest we remove this map.

cc @Vyom-Yadav for awareness.

[Vyom-Yadav]

Let's clean this up here first and later we can get this corrected in the PR.

[rashansmith]

Author confirmed release note is not needed.

[wendy-ha18]

Thanks @rashansmith , so it's good to remove this map

[Vyom-Yadav]

Removed that note

[wendy-ha18]

🔴 It seems like the Action required:.... couldn't been captured by krel in a few release notes, but this part is quite important for end-users.

According to this discussion from Release Announcement: kubernetes/website#51877 (comment). (view screenshot).

The PR #131837 should reserve the Action required:.... part as it will breaking behaviours of end-users and shouldn't be missed.

Static pods that reference API objects are now denied admission by the kubelet so that static pods would not be silently running even after the mirror pod creation fails.
ACTION REQUIRED: Prior to upgrade, ensure static pods are not referencing API objects such as ServiceAccounts, ConfigMaps, Secrets, ResourceClaims, CSIDrivers, PersistentVolumeClaims, or ClusterTrustBundles.

However the newest release-note-draft.md/json only include a part of it:

Static pods that reference API objects were denied admission by the kubelet so that static pods would not be silently running even after the mirror pod creation failed. (https://github.com/kubernetes/kubernetes/pull/131837, [@sreeram-venkitesh](https://github.com/sreeram-venkitesh)) [SIG Auth, Node and Testing]

Could you please also help to include the Action required: ... back to release note for this PR as well? 🙏

[Vyom-Yadav]

I don't see the following PRs in the release notes:

• [go] Bump dependencies, images and versions used to Go 1.24.6 and distroless iptables kubernetes#133516
• Clarify staging repository READMEs kubernetes#133570
• DRA allocator: fix data race around claimsToAllocate kubernetes#133587
• Fix storage counting all objects instead of objects for resource kubernetes#133604
• Make podcertificaterequestcleaner role feature-gated kubernetes#133409

[Vyom-Yadav]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rashansmith, Vyom-Yadav

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• releases/release-1.34/OWNERS [Vyom-Yadav]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment