PostHog: align ClickHouse/Kafka topology to Cloud + pin digests #8

Merged
founder merged 1 commit from codex/posthog-cloud-aligned into main 2026-07-20 07:24:09 +00:00
Owner

Define aux/ops/ai_events/sessions clusters + all warpstream named collections as single-node stand-ins so migrations run as authored and the schema stays Cloud-shaped; drop the cluster remaps; pin images by digest. 🤖 Generated with Claude Code

Define aux/ops/ai_events/sessions clusters + all warpstream named collections as single-node stand-ins so migrations run as authored and the schema stays Cloud-shaped; drop the cluster remaps; pin images by digest. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
posthog: align ClickHouse/Kafka topology to Cloud + pin image digests
Some checks failed
Release: If Needed / Check (Release Needed) (push) Successful in 5s
Deploy: API / Deploy (API) (push) Failing after 20s
Deploy: Web / Deploy (Web) (push) Failing after 1m41s
fb5c698be5
Reproduce PostHog Cloud's topology as single-node stand-ins so migrations run
as authored and the self-hosted schema stays Cloud-shaped (easier upgrades and
future migration), instead of remapping/omitting:

- remote_servers: add aux, ops, ai_events, sessions as single-node clusters
  (alongside the existing posthog* clusters), so ON CLUSTER migrations use their
  native Cloud cluster names.
- named_collections: define all Cloud Kafka collection names (msk_cluster +
  warpstream_calculated_events/cyclotron/ingestion/logs/metrics/replay/shared/
  traces), each pointed at the local broker; previously only 2 were defined and
  the rest were created ad hoc via SQL (not reproducible on a fresh install).
- env: drop the CLICKHOUSE_{AUX,AI_EVENTS,OPS}_CLUSTER remaps onto
  posthog_single_shard and set CLICKHOUSE_SATELLITE_CLUSTERS to Cloud's default
  (ai_events,aux,ops,sessions) now that those clusters exist.
- Pin posthog/posthog-node/capture images by sha256 digest (the 2026-07-19
  build verified to migrate cleanly, 308 CH tables) instead of :latest/:master,
  so upgrades are deliberate and never jump to an untested build mid-deploy.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
key-store/key.store!8
No description provided.