Prevent the Use of Let's Encrypt for Certificate Generation

[siddjellali]

Description:

I’m experiencing an issue with using Let's Encrypt as the certificate provider in my setup. I use Traefik as a reverse proxy to manage TLS certificates, but I’m getting a TLS error because Caddy starts without a valid certificate when deployed using the Helm Chart.

In my Docker Compose setup, a tls internal option was added to Caddy, which resolved the issue. Is it possible to add a similar tls internal option to the Helm Chart to ensure that Caddy can start properly without relying on Let's Encrypt? This would also prevent conflicts with Traefik.

Steps to Reproduce:

• Deploy the application using the Helm Chart with Caddy.
• Configure Traefik as the reverse proxy to handle TLS certificates.
• Observe that Caddy starts without a valid certificate, resulting in a TLS error.

Expected Result:

Caddy should use an internal TLS configuration (tls internal) to avoid the error and integrate correctly with Traefik.

Environment:

• Reverse Proxy: Traefik
• Deployment: Helm Chart
• Specific Configurations: TLS certificate management via Traefik

Proposed Solutions:

1. Add an option to the Helm Chart to enable a tls internal setting for Caddy, similar to the Docker Compose configuration.
2. Add an option to disable Caddy completely and expose the frontend service directly, allowing Traefik to manage reverse proxying and TLS certificates without conflicts.

[siddjellali]

Hi,

It's not exactly the same issue.
Can we propose something to disable caddy ?