[feature]: Self managed TLS support
@mguptahub is already working on this.
Since Oct 13, 2024.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Is there an existing issue for this?
- I have searched the existing issues
Summary
Self managed TLS support. For cases where an automatically generated certificate is not desired, and a certificate already exists.
Example, I have a wildcard certificate. It's already configured on my K8S cluster. I should be able to specify 'self managed', the certificate name as stored in K8S, and expect that to enable TLS support without any further configuration.
Why should this be worked on?
On demand certificate provisioning is not always desired (or possible to use). Running over http is not desirable in most cases.
The configuration changes to enable the above self_managed: true and certificate_name logic would be relatively small chart modifications, with a lot of upside (in my case at least).
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.
Assessment
This issue has not been assessed yet.