HTTP Request LEGO (K8s)
- By Canonical Telco
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 83 | 12 May 2024 | |
| latest/candidate | 83 | 12 May 2024 | |
| latest/beta | 83 | 12 May 2024 | |
| latest/edge | 83 | 12 May 2024 |
juju deploy httprequest-lego-k8s --channel edge
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
The LEGO DNS Agent
When using the httpreq plugin, the Lego client requires an HTTP Endpoint of a custom challenge solver. This Challenge Solver or DNS Agent should be able to solve the DNS-01 challenge by automating the creation and removal specific DNS records.
The DNS Agent will create a TXT DNS record that contains the value provided by the ACME Server on the fqdn required by the ACME Server. The agent should be able to do this upon request from the Lego Client on its API.
The agent should expose two endpoints, present and cleanup
To learn more on how to write a custom challenge solver for your DNS provider refer to LEGO documentation on writing a challenge solver.