Enhancements exception request for KEP-4317 PR #133242

[Taahir Ahmed]

• 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.

[Jordan Liggitt]

I'm +1 on merging the fixup PR, risk is negligible, PR is ready for merge, there's no additional delay.

On Tue, Jul 29, 2025 at 6:01 PM Sergey Kanzhelev <skanz...@google.com> wrote:

approve from sig node. Making the feature fully functionalu is important for alpha validation and the change is easy

/Sergey

[Sergey Kanzhelev]

approve from sig node. Making the feature fully functionalu is important for alpha validation and the change is easy

/Sergey

On Tue, Jul 29, 2025 at 2:16 PM Taahir Ahmed <ta...@google.com> wrote: