Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CertificateSigningRequest API #1513

Closed
liggitt opened this issue Jan 27, 2020 · 43 comments
Closed

CertificateSigningRequest API #1513

liggitt opened this issue Jan 27, 2020 · 43 comments
Assignees
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone

Comments

@liggitt
Copy link
Member

liggitt commented Jan 27, 2020

CertificateSigningRequest API

@liggitt liggitt self-assigned this Jan 27, 2020
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 27, 2020
@liggitt
Copy link
Member Author

liggitt commented Jan 27, 2020

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 27, 2020
@liggitt
Copy link
Member Author

liggitt commented Jan 27, 2020

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

@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 27, 2020

/milestone v1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 27, 2020
@jeremyrickard jeremyrickard added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 27, 2020
@jeremyrickard
Copy link
Contributor

jeremyrickard commented Jan 29, 2020

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.

@liggitt liggitt added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Jan 30, 2020
@liggitt
Copy link
Member Author

liggitt commented Jan 31, 2020

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

opened in #1536

@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020

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!

@liggitt
Copy link
Member Author

liggitt commented Feb 6, 2020

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

@jeremyrickard
Copy link
Contributor

jeremyrickard commented Feb 11, 2020

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!

@liggitt
Copy link
Member Author

liggitt commented Feb 11, 2020

@jeremyrickard
Copy link
Contributor

jeremyrickard commented Feb 11, 2020

Thanks @liggitt 🙇

@munnerz
Copy link
Member

munnerz commented Feb 18, 2020

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

@VineethReddy02
Copy link

VineethReddy02 commented Feb 21, 2020

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! :)

@jeremyrickard
Copy link
Contributor

jeremyrickard commented Mar 3, 2020

Thanks for getting those PRs merged @liggitt @munnerz

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

@liggitt
Copy link
Member Author

liggitt commented Mar 3, 2020

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

@jimmyjones2
Copy link

jimmyjones2 commented Mar 28, 2020

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?

@palnabarun palnabarun added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Apr 17, 2020
@liggitt
Copy link
Member Author

liggitt commented Apr 20, 2020

/milestone v1.19

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.18, v1.19 Apr 20, 2020
@liggitt
Copy link
Member Author

liggitt commented May 27, 2020

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

@savitharaghunathan
Copy link
Member

savitharaghunathan commented Jun 1, 2020

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!

@liggitt
Copy link
Member Author

liggitt commented Jun 1, 2020

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

@savitharaghunathan
Copy link
Member

savitharaghunathan commented Jun 1, 2020

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

Thanks for the update @liggitt :)

@msedzins
Copy link

msedzins commented Jun 3, 2020

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

@msedzins
Copy link

msedzins commented Jun 16, 2020

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

@liggitt
Copy link
Member Author

liggitt commented Jul 6, 2020

Doc PR is ready for review

@msedzins
Copy link

msedzins commented Jul 8, 2020

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.

@liggitt
Copy link
Member Author

liggitt commented Jul 8, 2020

yes, this is code complete

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 11, 2020

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

@kikisdeliveryservice kikisdeliveryservice removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 11, 2020
@liggitt
Copy link
Member Author

liggitt commented Sep 14, 2020

KEP update in #1984

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Sep 14, 2020

@liggitt: Closing this issue.

In response to this:

KEP update in #1984

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Development

No branches or pull requests