/sig auth

@jeremyrickard work is continuing on this API in 1.18, progressing in the beta state.

/milestone v1.18

Hey @liggitt as we were doing a review of all the items we were tracking last night, we noticed that the KEP for this is missing a test plan. Could you update the KEP and include that so that we can track for 1.18? Thanks and apologies for the very last minute request.

Could you update the KEP and include that so that we can track for 1.18?

opened in #1536

Hello, @liggitt, I'm 1.18 docs lead
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Yes, there will doc updates for the work done in this feature in 1.18

Hey @liggitt,

Just a friendly reminder that code freeze for 1.18 is March 05, 2020.

As we track toward code freeze, please list out/link to any PRs you are working on toward graduating this enhancement!

PRs in flight:

• Add signerName admission plugins kubernetes#86933
• CertificateSigningRequest 'signerName' field API additions kubernetes#86476

Thanks @liggitt 🙇

Additional PR in-flight for tracking: kubernetes/kubernetes#88246

Hello @liggitt
We are close to the docs placeholder PR deadline against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhancements much better.

Thanks! :)

Thanks for getting those PRs merged @liggitt @munnerz

Anything else to go before code freeze, or are you good now?

All the k/k PRs I'm aware of are complete. The docs PR is outstanding.

I've read the proposal, is the plan in the future for this to be able to automatically provision server certificates for services (like OpenShift) and client certificates for service accounts to be used by user applications?

/milestone v1.19

I will link PRs here and update the KEP format as I have the opportunity to.

Hi @liggitt , we are 12 days away from docs placeholder PR deadline. Does this PR needs any docs update? If so, placeholder PR against dev-1.19 branch is due by June 12th. Thanks!

the docs for this feature will be included in kubernetes/website#21108

the docs for this feature will be included in kubernetes/website#21108

Thanks for the update @liggitt :)

Hi @liggitt, thank you very much for your update.

Hi, @liggitt

This is a follow-up to the communication that went out to k-dev today. There has been a revision to the release schedule of v1.19 as follows.

Thursday, July 9th: Week 13 - Code Freeze
Thursday, July 16th: Week 14 - Docs must be completed and reviewed
Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released
Thursday, August 27th: Week 20 - Release Retrospective

You can find the revised Schedule in the sig-release Repo

Please let me know if you have any questions. 🖖

Doc PR is ready for review

Hi @liggitt , from what I can see this enhancement is Code complete so it's ready for Code freeze deadline which happens July 9th.
Please let me know if you think otherwise and there are any risks for that enhancement to be included in v.1.19.

yes, this is code complete

Hi @liggitt !

Enhancements Lead here. It looks like this KEP went stablein 1.19. Could you please update the KEP to have a status of implemented? Afterwards you can also close this issue once the PR updating it has merged?

Thanks!
Kirsten

KEP update in #1984

/close

@liggitt: Closing this issue.