Prombench users getting certificate warnings on Chrome

[geekodour]

Maybe we should be switch to HTTPS or just get rid of the fake certificate in use.

Common Name (CN)	Kubernetes Ingress Controller Fake Certificate
Organisation (O)	Acme Co
Organisational Unit (OU)	<Not Part Of Certificate>

[geekodour]

@krasi-georgiev do you think we need this? we're probably using a wildcard certificate, i was wondering if we should be using be using the *.prometheus.io wildcard certificate or gets new certificate on specific subdomain, if the ssl provider allows that?

[roidelapluie]

Get a specific certificate I'd say

[krasi-georgiev]

@roidelapluie get it how? I am not sure how is this handled for prometheus.io?

Unless certificate handling can be easily automated I would to postpone spending time on this and focus on other higher priorities issues

[roidelapluie]

Caddy can automate that, aren't we using that?

[krasi-georgiev]

So IIUC this automation needs to be handled by the Grafana UI, no?
In other words, the Grafana UI needs to use Caddy as a library to automate the HTTPS cert handling.

[roidelapluie]

Oh caddy is a reverse proxy. I was assuming that caddy was our ingress controller.

[roidelapluie]

Alright, here is the confusion. We use caddy in https://demo.do.prometheus.io/ but not in prombench.

[krasi-georgiev]

ok so the action item is - use Caddy as a proxy server for prombench.
Again I think our top priority should be to make the current dashboards and tests more useful then anything else.