docs: correct dev-environment topology in CLAUDE.md#524
Merged
Conversation
The dev environment was migrated to Docker Desktop Kubernetes (#520/#521), but CLAUDE.md still described a kind cluster with the database and Redis running as containers "external to the cluster." That stale description caused a misdiagnosis when the in-cluster PostgreSQL PVC came up empty: the real data was assumed lost when it was actually stranded in the old host Docker volume the new topology no longer mounts. Update both occurrences to reflect reality: - Default CLUSTER=docker-desktop (k3s also supported) - server, PostgreSQL, Redis, and NATS all run in-cluster in the tmi-platform namespace (Deployments + StatefulSets) - PostgreSQL data persists in a Kubernetes PVC (data-postgres-0), NOT a host Docker volume; re-provisioning the PVC starts from an empty DB - With DB=oracle the database is an external managed Oracle ADB - orchestration is via scripts/devenv.py; manifests under deployments/k8s/dev/<cluster>/ Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Kk9GxWS9EpazjbwBKfMpUX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The dev environment was migrated to Docker Desktop Kubernetes (#520/#521), but
CLAUDE.mdstill described a kind cluster with the database and Redis running as containers "external to the cluster."That stale description directly caused a misdiagnosis during a debugging session: when the in-cluster PostgreSQL PVC came up empty, the real data was assumed lost — when it was actually stranded in the old host Docker volume (
tmi-postgres-data) that the new topology no longer mounts.Changes
Corrects both occurrences to reflect the real topology:
CLUSTER=docker-desktop(k3s also supported viaCLUSTER=k3s)tmi-platformnamespace (Deployments + StatefulSets)data-postgres-0), not a host Docker volume — re-provisioning the PVC starts from an empty database (the exact trap that caused the misdiagnosis)DB=oraclethe database is an external managed Oracle ADB, not in-clusterscripts/devenv.py; manifests live underdeployments/k8s/dev/<cluster>/Docs-only change (Markdown) — no build/test/lint gates apply.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Kk9GxWS9EpazjbwBKfMpUX