l3montree-dev / l3montree-dev/devguard
consider automatic ingress tls
@seb-kw is already working on this.
Since Aug 19, 2026.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
We have a loadbalancer for our k8s cluster which is capable to manage a default TLS certificate (and custom TLS certificates, too) based on a wildcard domain. For this we don't have to use a tls block in the ingresses. The TLS secret is stored outside the cluster and even the namespace. Btw: the loadbalancer makes an 302-redirect to https endpoint if it's called via "http". But because of the strict-origin-when-cross-origin header (CORS) it's running into an error for the login or registration button.
Unfortunately the kratos-config.yaml uses "https" protocol only when .Values.web.ingress.tls=true (it would actually be sufficient but then you need a tls-secret in the namespace).
I want to have the option to tell the chart that it's automatically TLS (https protocol). OR: tls=true but without the need to provide a tls-secret, i.e. so no tls block is written into ingress definition if no secret is given.
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.