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

Add option to generate CSRs to kubeadm alpha phase certs #794

Closed
randomvariable opened this issue May 9, 2018 · 4 comments
Closed

Add option to generate CSRs to kubeadm alpha phase certs #794

randomvariable opened this issue May 9, 2018 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone

Comments

@randomvariable
Copy link
Member

randomvariable commented May 9, 2018

FEATURE REQUEST

Certificate generation is currently handled completely internally of kubeadm, although there is support for externally generated certificates (if kubeadm finds certificates but not the private CA key).

Some users of external CAs could consume CSRs generated by kubeadm, which is fed with node information, and pass on those CSRs to external CAs, store the results in the appropriate place and allow kubeadm to use these as any other external CA.

The workflow would be something like:

  • Generate config file
  • kubeadm alpha phase certs all --csr-only --config <path to config> --csr-dir <somewhere>
    • kubeadm generates CSRs in appropriate directory, also outputs where they should go on disk
  • Externally send CSRs to external CAs
  • Externally place signed certs in the correct location
  • Continue with kubeadm init workflow

Versions

kubeadm version (use kubeadm version):
git commit: 13f3c7c7ca5d79edeb82a6075b3743c788a3ca4a (pre 1.11 master at time of writing this issue)

Environment:
N/A

cc @liztio as per Slack conversation.

@randomvariable
Copy link
Member Author

/kind feature
/sig cluster-lifecycle

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. labels May 9, 2018
@timothysc
Copy link
Member

/assign @liztio

@timothysc timothysc added this to the v1.12 milestone Jul 3, 2018
@timothysc timothysc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 3, 2018
@timothysc timothysc modified the milestones: v1.12, v1.13 Aug 30, 2018
@timothysc
Copy link
Member

We're going to have to punt this to 1.13 due to code freeze.

@timothysc timothysc added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 30, 2018
@liztio liztio added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Nov 2, 2018
@neolit123
Copy link
Member

solved in:
kubernetes/kubernetes#70809

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

5 participants