charts-clickhouse
charts-clickhouse copied to clipboard
PostHog
Automated test for deploying to a different namespace
Is your feature request related to a problem?
We have broken chart deployment to namespaces other than "posthog" various times.
Describe the solution you'd like
Add a test that tries to deploy with different namespace name & check everything came up.
Describe alternatives you've considered
as is; use a different namespace during release testing.
Additional context
Thank you for your feature request – we love each and every one!
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
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?
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.
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.