Kube-Lego automatically requests certificates for Kubernetes Ingress resources from Let's Encrypt.
This chart is fully based on the examples found on their github pages.
It uses version 0.1.2 of the corresponding docker image.
This chart needs a Nodeport, so that the letsencrypt server can contact us. This is configured via the properties .Values.extNodePort as well as .Values.legoKubeApiUrl.
Get this Chart
Our central repository is located at:
https://devopsku.be/charts, please configure this in your helm installation (via
helm repo add). Then you can download and install this chart using the usual helm procedure (see Using Helm).
If you would like to contribute and/or like to make changes on this chart, please clone this repo via:
git clone https://github.com/devopskube/devopskube.git
Installing the chart
The installation-instructions can be found on the above mentioned Using Helm page.
The following tables lists the configurable parameters of the SonarQuebe chart and their default values.
|The email with which the certs are generated at LetsEncrypt||
||The Url with which the certificates are created, staging by default||
||Port of the container||
||Url where the letsencrypt server contacts us||
||The external port, where letsencrypt server contacts us||
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install --name my-kube-lego -f values.private.yaml kube-lego-x.x.x.tgz
Tip: You can use the default values.yaml
Tip: To use this in a production environment (not recommended by now), you should set the lego_url property to the corresponding production url of letsencrypt (https://acme-v01.api.letsencrypt.org/directory).
This chart stores the configuration inside its own configmap, no further persistence-store is necessary.
To check the availabilty of the kube-lego key, you can check the following url: