Guido Iaquinti

> > Edit #2: a bit related to this, I've opened #635 to add a PgBouncer service FQDN. We should likely do the same for all the services so that...

👋 Hey @charlrvd, can you please share your `values.yaml` (redacting any sensitive information)?

Related to https://github.com/PostHog/charts-clickhouse/pull/439

> This pull request breaks the backward compatibility of values. Can we start by simply adding tolerations and nodeSelector to migrations? This is an old PR that we still might...

> Then maybe make a separate PR with only tolerations and nodeSelector to migrations ? I need these options now, but doing it only in my fork is not convenient...

> Not necessarily a blocker, but a thing to consider here - can we give actionable feedback if the install fails in a simple way? > > Without `--debug` I...

👋 @SuperTux88 and thank you for your contribution! We currently vendor everything in `charts/posthog/templates/clickhouse-operator` via [scripts/clickhouse_operator_sync.sh](https://github.com/PostHog/charts-clickhouse/blob/main/scripts/clickhouse_operator_sync.sh) as there isn't an Helm chart for the `clickhouse-operator`. Due to this we usually...

👋 Hi @dvirp-dt! Thank you for opening this issue. This looks somehow similar to https://github.com/PostHog/charts-clickhouse/pull/342 (cc @navi86) where [my main concern](https://github.com/PostHog/charts-clickhouse/pull/342#issuecomment-1084667881) was about customising an upstream dependency instead of directly...

In the meantime, https://github.com/PostHog/charts-clickhouse/pull/371 will make the container image fixed so you should not experience unplanned version upgrade in case a newer version will use the same tag.

> How would you suggest editing this image in case we have to? In the meantime, if you can make the deployment process two steps, you could probably first render...