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

Refactor csr/cert generation for fewer steps and cluster use #1

Open
siliconalchemy opened this issue Dec 5, 2016 · 2 comments
Open

Comments

@siliconalchemy
Copy link
Owner

Currently CSRs are generated on the client and then shipped to the puppetmaster to request the cert. It involves many puppet runs - 2 on the client for the initial CSR, 2 on the puppetmaster for the request and signing, and at least one on the client to collect the certs.
Further, if a CSR is requested for the same domain from multiple nodes it will generate a duplicate resource and any further puppet runs will crash:
bzed#26

Look to refactor how a CSR is generated and certs are requested and deployed, to reduce the number of steps and allow certs to be requested/deployed from multiple nodes.

@siliconalchemy
Copy link
Owner Author

@siliconalchemy
Copy link
Owner Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant