-
Notifications
You must be signed in to change notification settings - Fork 3
Tracing protocol is HTTP even though tempo-k8s is related to self-signed-certificates #153
Comments
Quick passby thought: did you add certificates relation to traefik too? Maybe this one was missing. |
@mmkay I related traefik with self-signed-certificates (on both |
Not immediately but you can check Administration -> Datasources and check what URL is shown next to Tempo's datasource. In your setup I'd expect |
@shayancanonical Could you verify if the certificate is being copied in the charm container of This way, the charm should trust the passed CA. |
Hi @shayancanonical are you still experiencing this issue?? |
@Abuelodelanada @lucabello Can confirm that the issue is still reproducible (even after confirming that the cert is added as a result of running We have a similar use case in MySQL: MySQL relates to self-signed-certificates operator and instead of asking the app related to MySQL to get the cert by relating to the self-signed-certificates operator, MySQL passes the cert to the client app through the databag. The reason I mention this is because doing so would greatly simplify our implementation and reduce the probability of human error. Logs while reproducing:
|
issue was that traefik wasn't related to SSC. closing this, and opening a different ticket instead to see if we can surface this situation better |
Bug Description
The tracing protocol that is expected is HTTP even though tempo-k8s is related to self-signed-certificates. Furthermore, even though we are using
charm_tracing_config
, tracing is enabled but server_cert is returning None. Since tempo-k8s is using HTTPS, the mysql charm tries to export spans to tempo and fails continuously (leading to the charm getting stuck with the same hook handler - which does not return as span exporting is retrying infinitely)To Reproduce
In k8s model:
In lxd model:
Environment
juju: 3.4.3
microk8s: MicroK8s v1.27.13 revision 6744
lxd: 6.1
ubuntu 22.4.3 LTS
Relevant log output
Additional context
Certificate retrieved in mysql charm:
databag from the perspective of mysql (note that protocol type is http):
The text was updated successfully, but these errors were encountered: