replicatedhq / replicatedhq/kURL
Feature: Support ACME cert creation on the TLS page of kURL
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 809
- Forks
- 81
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 20
Description
The TLS page of kURL prompts to upload a key and cert to secure the Admin Console, or to continue with a self signed cert. For clusters that are connected to the public internet, we could start a HTTP Challenge server and provision a cert from LetsEncrypt or another ACME provider here. Then, the kURL proxy service should also be responsible for renewing the cert from the issuer before expiration.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the TLS page and kURL proxy service described in the issue, then trace how certificates are currently uploaded or self-signed. Define the HTTP Challenge flow, ACME provider interaction, and renewal behavior; done means the TLS page can provision a public certificate and the proxy renews it before expiration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100