[OpenTelemetry] Enable TLS/HTTPS for Grafana container started by Arconia Observability

[SekouSallah]

Describe the problem/challenge you have

When using Arconia Observability (OpenTelemetry integration), a Grafana container (grafana/otel-lgtm) is automatically started for local development and testing. This container is always exposed over plain HTTP on a random port (~33383). There is currently no built-in way to run it with TLS/HTTPS, which is a security concern even in local development and especially when the stack is used in production-like or shared environments.

Describe the solution you'd like

Add a simple configuration option in application.properties (or via environment variables) to enable TLS for the auto-started Grafana container:

arconia.observability.grafana.tls.enabled=true
arconia.observability.grafana.tls.certificate=/path/to/tls.crt
arconia.observability.grafana.tls.private-key=/path/to/tls.key

When enabled, Arconia should:

• Mount the provided certificate and key files into the Grafana container
• Automatically configure Grafana to serve over HTTPS

This would make Grafana accessible securely out of the box, without requiring manual container configuration or external reverse proxies.

Thank you!

Anything else you would like to add

No response

I assert that this issue is relevant for Arconia

• I assert that this is a feature request and not a support request. If you need assistance, please use GitHub Discussions.
• I assert that this is not a duplicate of an existing issue.
• I assert that I have read the Arconia Code of Conduct and agree to abide by it.

[ThomasVitale]

@SekouSallah thanks so much for trying out Arconia and for raising this feature request. We're currently planning a series of improvements about the Dev Services (tracked here: #159) and I'm trying to understand a bit better the use case where TLS is needed for the Dev Services and see if we can address this in the next iteration.

Being a development tool, Dev Services are only expected to be run locally during development and/or when running tests, where there shouldn't be security concerns. You mentioned "production-like or shared environments". Could you elaborate on that? I'm interested in understanding better your scenario.

In general, the Arconia Dev Services are based on the Service Connections features in Spring Boot. There is TLS support there for some services (https://docs.spring.io/spring-boot/reference/testing/testcontainers.html#testing.testcontainers.service-connections.ssl). For example, the OpenTelemetry services are not included. But I'm looking into how to support in Arconia at least what Spring Boot supports, regarding TLS.