Allow PostHog and ClickHouse to be in different Namespaces

[terrymunro]

Is your feature request related to a problem?

Hi, I'm not sure if this is a minor bug or a feature request, but I had a problem where the Kafka tables in ClickHouse weren't connecting because I had connected PostHog to an existing ClickHouse Cluster which happened to be in a different namespace. I manually dropped and recreated the Kafka tables with the namespace added to the URL, which fixed the issue.

Describe the solution you'd like

In the _helpers.tpl maybe it could default to always using the full form, for example: Namespace: analytics Release Name: prod Before URL: prod-posthog-kafka:9092 After URL: prod-posthog-kafka.analytics:9092

I'm making an assumption here that, by changing it there, it would change the URL set by the migrate job that creates the tables.

Describe alternatives you've considered

I probably could have set this full form URL myself in the values.yml had I known that it would be a problem, so an alternative could be just to document it.

Additional context

• I'm new to both PostHog and Kubernetes.
• I've run into other issues before because of the way I've tried to set things up.

Thanks guys, love your work.

[macobo]

Hi! I've documented using an external clickhouse cluster here: https://github.com/PostHog/charts-clickhouse/pull/276, which depends on https://github.com/PostHog/charts-clickhouse/pull/276 (release 13.0.0)

Note that a few changes are required for it to work that aren't yet in a stable posthog release, see the linked issue for details.