DevFW-CICD/ingress-nginx-helm
12
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Replace kube-lego docs with cert-manager (#7659)

Browse source 
Since kube-lego has not been maintained in quite a while,
I thought it would be best to remove the documentation about it
and replace it with information about cert-manager.
This commit is contained in:
Jennifer Kirsch 2021-09-19 20:06:08 +02:00 committed by GitHub
parent c2fe736d48
commit 314cc6c2dc
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 24 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

38
docs/user-guide/tls.md
View file

@ -87,24 +87,33 @@ annotation in the particular resource.
This can be achieved by using the `nginx.ingress.kubernetes.io/force-ssl-redirect: "true"` This can be achieved by using the `nginx.ingress.kubernetes.io/force-ssl-redirect: "true"`
annotation in the particular resource. annotation in the particular resource.
## Automated Certificate Management with Kube-Lego ## Automated Certificate Management with cert-manager
!!! tip [cert-manager] automatically requests missing or expired certificates from a range of
Kube-Lego has reached end-of-life and is being [supported issuers][cert-manager-issuer-config] (including [Let's Encrypt]) by monitoring
replaced by [cert-manager](https://github.com/jetstack/cert-manager/). ingress resources.
[Kube-Lego] automatically requests missing or expired certificates from [Let's Encrypt] To set up cert-manager you should take a look at this [full example][full-cert-manager-example].
by monitoring ingress resources and their referenced secrets.
To enable this for an ingress resource you have to add an annotation: To enable it for an ingress resource you have to deploy cert-manager, configure a certificate
issuer update the manifest:
```console ```yaml
kubectl annotate ing ingress-demo kubernetes.io/tls-acme="true" apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-demo
annotations:
cert-manager.io/issuer: "letsencrypt-staging" # Replace this with a production issuer once you've tested it
[..]
spec:
tls:
- hosts:
- ingress-demo.example.com
secretName: ingress-demo-tls
[...]
``` ```
To setup Kube-Lego you can take a look at this [full example][full-kube-lego-example].
The first version to fully support Kube-Lego is Nginx Ingress controller 0.8.
## Default TLS Version and Ciphers ## Default TLS Version and Ciphers
To provide the most secure baseline configuration possible, To provide the most secure baseline configuration possible,
@ -136,10 +145,11 @@ data:
[full-kube-lego-example]:https://github.com/jetstack/kube-lego/tree/master/examples
[Kube-Lego]:https://github.com/jetstack/kube-lego
[Let's Encrypt]:https://letsencrypt.org [Let's Encrypt]:https://letsencrypt.org
[ConfigMap]: ./nginx-configuration/configmap.md [ConfigMap]: ./nginx-configuration/configmap.md
[ssl-ciphers]: ./nginx-configuration/configmap.md#ssl-ciphers [ssl-ciphers]: ./nginx-configuration/configmap.md#ssl-ciphers
[SNI]: https://en.wikipedia.org/wiki/Server_Name_Indication [SNI]: https://en.wikipedia.org/wiki/Server_Name_Indication
[mozilla-ssl-config-old]: https://ssl-config.mozilla.org/#server=nginx&config=old [mozilla-ssl-config-old]: https://ssl-config.mozilla.org/#server=nginx&config=old
[cert-manager]: https://github.com/jetstack/cert-manager/
[full-cert-manager-example]:https://cert-manager.io/docs/tutorials/acme/ingress/
[cert-manager-issuer-config]:https://cert-manager.io/docs/configuration/