Enhancements exception request for KEP-4317 PR #133242

21 views
Skip to first unread message

Taahir Ahmed

unread,
Jul 29, 2025, 5:16:57 PMJul 29
to kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-sig-release, Jordan Liggitt, Sergey Kanzhelev
  • Enhancement name: Pod Certificates
  • Enhancement status (alpha/beta/stable): Alpha
  • SIG: auth
  • k/enhancements repo issue #: 4317
  • PR #’s: 133242
  • Additional time needed (in days): 2
  • Reason this enhancement is critical for this milestone:
    • Not critical -- alpha feature launch
  • Risks from adding code late: (to k8s stability, testing, etc.)
    • Low: All feature code is behind feature gates and an Alpha API
  • Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
    • The enhancement is already landed in 1.34
    • Manual end-to-end testing of the feature after it merged found a bug that keeps the feature from working.
    • This bug would have been caught by an automated end-to-end test
    • End-to-end tests could not land in the same PR as the main implementation because they require new agnhost functionality.
    • The fix in PR 133242 has been verified with manual end-to-end testing.
    • Without the fix, interested parties will not be able to try the Pod Certificates alpha feature, delaying feedback and progress towards GA.

Sergey Kanzhelev

unread,
Jul 29, 2025, 6:01:08 PMJul 29
to Taahir Ahmed, kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-sig-release, Jordan Liggitt
approve from sig node. Making the feature fully functionalu is important for alpha validation and the change is easy

/Sergey

Jordan Liggitt

unread,
Jul 29, 2025, 6:02:20 PMJul 29
to Sergey Kanzhelev, Taahir Ahmed, kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-sig-release
I'm +1 on merging the fixup PR, risk is negligible, PR is ready for merge, there's no additional delay.

Vyom Yadav

unread,
Jul 31, 2025, 6:31:49 AMJul 31
to kubernetes-sig-release
Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0].
The additional time asked in this request is invalid as code freeze started at 02:00 UTC 25 July - this additional time field is supposed to reflect time from code freeze. 
The related PR has already been merged. 

If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Vyom Yadav
v1.34 Release Team Lead

[0] https://kubernetes.slack.com/archives/C2C40FMNF/p1753860539604579 
Reply all
Reply to author
Forward
0 new messages