mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 13:36:02 +03:00
[GH-ISSUE #350] [Question] mkcert vs cert-manager #230
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#230
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @scheung38 on GitHub (Mar 9, 2021).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/350
Are these two providing the same functionality in terms of cert management?
@noelforte commented on GitHub (Apr 5, 2021):
If you're referring to https://cert-manager.io/ then no,
mkcertis a tool aimed at local development to automate the generation of untrusted certificates from a local certificate authority, while cert-manager appears to be a tool for creating certificates for deployment on a Kubernetes cluster. Therefore these 2 are not interchangeable and also mkcert wasn't designed to run in production environments as the certs and CA's it makes need installation on all clients in order to work.@jsponz commented on GitHub (Apr 14, 2021):
@noelforte what is your recommendation for a production environment?
Thanks,
Jorge
@noelforte commented on GitHub (Apr 15, 2021):
@jsponz seems a bit off-topic for this issue...nevertheless it depends on what you're trying to do. If you're looking to secure a small site with TLS then Let's Encrypt or any other ACME CA is the best option. For larger environments or enterprise use, your mileage will definitely vary.