Paweł Krupa

This needs a bit more thinking as we currently rely on this mechanism in tobs.

> We can close this issue, once we bump the timescaledb-single Helm chart and update tobs. Let's just merge this as we'll bump those components either way.

This issue is not about kubernetes, but about gathering tracing data from components **shipped** with tobs like promscale, prometheus (Issue about kubernetes tracing data is in https://github.com/timescale/tobs/issues/395.). Basically it allows...

> with production best practices i.e without HA. Lack of HA is violating production best practices. Instead we can offer "developer" version which is not having HA and can be...

[Slack discussion](https://iobeam.slack.com/archives/C02V9UDHJM8/p1651149524323509) was not about adding nightly tests, but about adding nightly release channel for promscale (which is a blocker for this task) and then e2e testing if ingestion through...

Related to https://github.com/timescale/tobs/issues/288

We can use `up` application to test the data flow (cc @onprem)

Possible test sequence: 1) provision DB with helm chart 2) compose DBURI 3) use DBURI from previous points as an external database

Depends on https://github.com/timescale/tobs/issues/473

> Any reason why we are scoping this task into promscale-on-cloud epic? I see it as more related to Tobs production readiness epic. It should be part of both. From...