Automated test for deploying to a different namespace about charts-clickhouse HOT 4 OPEN

Hi there, we recently came upon this issue while setting up our self-hosted deployments to AWS. We want to deploy a Sandbox environment alongside Production within the same k8s Cluster, matching Prod as closely as possible so we can test out any changes or upgrades.

We attempted to deploy both Sandbox and Production first using different namespaces, but ran into the issues that I assume were the impetus for this GH Issue. We then tried deploying the charts with the same release name, but into different namespaces, but ran into errors that resources already exist.

Any movement on a fix for this would be greatly appreciated.

PH Version: 1.35.0
k8s Version: 1.21.9

from charts-clickhouse.

I would encourage different k8s clusters for sandbox and test. To avoid potential problems of sandbox taking away resources from prod.
Regarding the problems you ran into could you provide more details?

from charts-clickhouse.

When we tried deploying the helm chart into a namespace named posthog-prod, the Kafka pod entered into an endless crash loop while trying to connect to ClickHouse.

from charts-clickhouse.

When we tried deploying the helm chart into a namespace named posthog-prod, the Kafka pod entered into an endless crash loop while trying to connect to ClickHouse.

You need to update https://github.com/PostHog/charts-clickhouse/blob/main/charts/posthog/values.yaml#L575 Unfortunately we haven't found a way to have that work natively.

That said I'd like to repeat my suggestion to use different clusters as there can be various problems now or in the future as running two instances in the same cluster it's not something we specifically support. This issue was mainly about having a single instance of Posthog running just in a different namespace.

from charts-clickhouse.