Paweł Krupa

Seems like the issue is with insufficient amount of resources: ``` 2022-08-16T17:48:13.4171151Z Warning FailedScheduling 4m36s (x5 over 15m) default-scheduler 0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are...

I opened raw logs from one of the CI runs and it was there. However right now it is no longer present.

The error you are seeing is most likely related to a slow startup of timescaledb pod (due to very large image size). For helm installation method I recommend increasing timeout...

To consider: do we want to have it enabled by default or not.

We are waiting for timescaledb-tune to support profiles and after that, we're going to include a said profile to be enabled by default.

> Is this supposed to be Draft PR? Yes, I am still working on it ;)

Yeah, I used draft PR exactly to catch such issues and figure out what next steps need to be done. I didn't want (or had time) to figure out the...

I can confirm this is the case. It is why we are skipping validation of CRDs in kube-prometheus (https://github.com/prometheus-operator/kube-prometheus/blob/main/Makefile#L43).

This should've been fixed in latest helm chart release after https://github.com/timescale/helm-charts/pull/327 was merged. If you find that the problem is still happening in your environment, please reopen this ticket.

Multinode helm chart is deprecated and not supported anymore. If you want to see this chart supported then we are looking for community maintainers - https://github.com/timescale/helm-charts/tree/master/charts/timescaledb-multinode#call-for-maintainers