Audit 1.30 Release for dropped Enhancements post-Enhancements Freeze

[kikisdeliveryservice]

The Project Board for 1.30 release tracks all KEPs removed from milestone at any phase of the release:
https://github.com/orgs/kubernetes/projects/175/views/1?filterQuery=status%3A%22Removed+from+Milestone%22+

In furtherance of investigating the rc of why in certain cases the kep.yaml is not a reliable source of truth (kubernetes/community#7777), let's get some hard numbers on what KEPs passed enhancements freeze but did not make it through docs freeze.

Deliverable:

• list of keps that made it past enhancements freeze but not code freeze
• list of keps that made it past code freeze but not enhancements freeze

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten