|
1 | 1 | --- |
2 | 2 | title: cert-manager |
3 | | -description: cert-manager documentation homepage |
| 3 | +description: | |
| 4 | + cert-manager creates TLS certificates for workloads in your Kubernetes or OpenShift cluster and renews the certificates before they expire. |
4 | 5 | --- |
5 | 6 |
|
6 | | -cert-manager adds certificates and certificate issuers as resource types in |
7 | | -Kubernetes clusters, and simplifies the process of obtaining, renewing and |
8 | | -using those certificates. |
| 7 | +cert-manager creates TLS certificates for workloads in your Kubernetes or OpenShift cluster |
| 8 | +and renews the certificates before they expire. |
9 | 9 |
|
10 | | -It can issue certificates from a variety of supported sources, including |
11 | | -[Let's Encrypt](https://letsencrypt.org), [HashiCorp Vault](https://www.vaultproject.io), |
12 | | -and [Venafi](https://www.venafi.com/) as well as private PKI. |
| 10 | +cert-manager can obtain certificates from a [variety of certificate authorities](configuration/issuers.md), including: |
| 11 | +[Let's Encrypt](configuration/acme/README.md), [HashiCorp Vault](configuration/vault.md), |
| 12 | +[Venafi](configuration/venafi.md) and [private PKI](configuration/ca.md). |
13 | 13 |
|
14 | | -It will ensure certificates are valid and up to date, and attempt to |
15 | | -renew certificates at a configured time before expiry. |
16 | | - |
17 | | -It is loosely based upon the work of |
18 | | -[kube-lego](https://github.com/jetstack/kube-lego) and has borrowed some |
19 | | -wisdom from other similar projects such as |
20 | | -[kube-cert-manager](https://github.com/PalmStoneGames/kube-cert-manager). |
| 14 | +With cert-manager's [Certificate resource](usage/certificate.md), the private key and certificate are stored in a Kubernetes Secret |
| 15 | +which is mounted by an application Pod or used by an Ingress controller. |
| 16 | +With [csi-driver](usage/csi-driver.md), [csi-driver-spiffe](usage/csi-driver-spiffe.md), or [istio-csr](usage/istio-csr.md) , |
| 17 | +the private key is generated on-demand, before the application starts up; |
| 18 | +the private key never leaves the node and it is not stored in a Kubernetes Secret. |
21 | 19 |
|
22 | 20 |  |
23 | 21 |
|
|
0 commit comments