prole/CLAUDE.md

CLAUDE.md — prole project context

Loaded automatically by Claude Code (CLI and IntelliJ plugin) as project context.

---

Dual-cluster GKE architecture

This project uses two separate GKE Standard clusters in us-west3, both currently provisioned with e2-standard-2 × 3 nodes (2 vCPU / 8 GB each, ~7.1 GB allocatable). Verify with gcloud container clusters list — knoe/core/actions.py still carries an e2-small default for the app cluster but the live cluster is e2-standard-2.

Cluster	Context	Role
knoe-dev-0	gke_plenary-truck-485623-p7_us-west3_knoe-dev-0	App cluster — Garage, registry, OpenBao, Kong, GitLab, monitoring
knoe-cnpg-0	gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0	DB cluster — CNPG/PostgreSQL only (note: conf/gke.cfg currently deploys this as knoe-dev-cnpg-0; the code default remains knoe-cnpg-0)

Storage quota: the project has SSD_TOTAL_GB = 300 GB in us-west3, fully consumed by CNPG. All non-CNPG PVCs must use standard (pd-standard / HDD) — not standard-rwo / premium-rwo, which are SSD-backed and will fail to provision with a quota error. GITLAB_GITALY_STORAGE_CLASS = standard is set in conf/gke.cfg accordingly.

Resource allocation

Resource	Cluster	Namespace
CNPG operator	knoe-cnpg-0	cnpg-system
PostgreSQL cluster (knoe-db)	knoe-cnpg-0	knoe-db-0
Barman Cloud plugin	knoe-cnpg-0	cnpg-system
cert-manager	knoe-cnpg-0	cert-manager
Garage (S3 object store)	knoe-dev-0	knoe-system
Registry	knoe-dev-0	knoe-system
OpenBao	knoe-dev-0	knoe-system
Kong API gateway	knoe-dev-0	knoe-system
Monitoring	knoe-dev-0	monitoring

Garage runs ONLY in knoe-dev-0. Do NOT deploy Garage to knoe-cnpg-0.

CNPG backups → GCS (not Garage)

Backups use GCS with Workload Identity (not Garage):

• Data bucket: gs://knoe-0-backups/
• WAL bucket: gs://knoe-0-wal/
• GCP SA: cnpg-backup@plenary-truck-485623-p7.iam.gserviceaccount.com
• K8s SA: cnpg-backup-sa in knoe-db-0 (annotated with WI)
• ObjectStore manifest: k8s/prole/knoe-db-barman-objectstore-gcs.yaml

Setup script: etc/init_cnpg_gke.sh (creates buckets, GCP SA, WI binding, applies CNPG cluster).

---

Service mesh (Cloud Service Mesh / Istio)

Both clusters are registered in the knoe-0 GCP fleet with automatic Cloud Service Mesh management. This is automated in scripts/reset_clusters.sh (Phase 7) — no longer requires GCP web console.

# Check mesh provisioning status (~10 min after cluster creation):
gcloud container fleet mesh describe --project=plenary-truck-485623-p7

# Manual re-registration if needed:
gcloud container fleet memberships register knoe-dev-0 \
  --gke-cluster=us-west3/knoe-dev-0 \
  --enable-workload-identity \
  --project=plenary-truck-485623-p7
gcloud container fleet mesh update \
  --management=automatic \
  --memberships=knoe-dev-0 \
  --project=plenary-truck-485623-p7

---

install.sh / deploy.sh pre-flight checklist

conf/gke.cfg (interactive installer — ./install.sh)

Before running ./install.sh (especially "Initialization Scripts"), confirm these are correct:

[Inputs]
init_cluster.app_cluster_kubecontext = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
init_cluster.db_cluster_kubecontext  = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0
env_setup.APP_CLUSTER_KUBECONTEXT    = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
env_setup.DB_CLUSTER_KUBECONTEXT     = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0

[Global]
KUBECONTEXT = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
APP_CLUSTER_KUBECONTEXT = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
DB_CLUSTER_KUBECONTEXT  = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0
CNPG_ELIGIBLE_NODES = <comma-separated node names from knoe-cnpg-0>

conf/service/prod.cfg (unattended deploy — ./deploy.sh)

Same cluster context entries are required here too:

[Inputs]
init_cluster.app_cluster_kubecontext = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
init_cluster.db_cluster_kubecontext  = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0
env_setup.APP_CLUSTER_KUBECONTEXT    = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
env_setup.DB_CLUSTER_KUBECONTEXT     = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0

[Global]
KUBECONTEXT = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
APP_CLUSTER_KUBECONTEXT = gke_plenary-truck-485623-p7_us-west3_knoe-dev-0
DB_CLUSTER_KUBECONTEXT  = gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0
ARTIFACT_REGISTRY = us-west3-docker.pkg.dev/plenary-truck-485623-p7/knoe-system
SERVICE_NAMESPACE = knoe-system
REGISTRY_NAMESPACE = knoe-system

Why these matter: Milestone._get_script_env() (in knoe/milestone.py) reads these to set KUBECONTEXT=app_ctx for common services and DB_CLUSTER_KUBECONTEXT=db_ctx for CNPG ops. Without them, all kubectl calls use the ambient context, which may be the DB cluster.

Missing init_cluster.app_cluster_kubecontext → _cluster_kubecontext("app") returns "" → installer falls back to Global.KUBECONTEXT for both app and db environments → Garage deploys to knoe-cnpg-0 (wrong).

Get current CNPG node names

kubectl --context=gke_plenary-truck-485623-p7_us-west3_knoe-cnpg-0 get nodes -o name

---

Key scripts

Script	Purpose
scripts/reset_clusters.sh	Delete + recreate both GKE clusters (e2-standard-2 × 3 each)
scripts/patch_garage_cross_cluster.sh	Remove garage from DB cluster, configure GCS barman ObjectStore
etc/init_cnpg_gke.sh	Provision CNPG on GKE with GCS backup via Workload Identity
etc/init_cnpg_backup.sh	Configure barman plugin + trigger initial backup

---

Cluster code constants (knoe/core/actions.py)

DEFAULT_APP_CLUSTER_NAME    = "knoe-dev-0"
DEFAULT_DB_CLUSTER_NAME     = "knoe-cnpg-0"          # also: DEFAULT_CNPG_CLUSTER_NAME
DEFAULT_APP_CLUSTER_MACHINE_TYPE = "e2-small"        # STALE — live app cluster is e2-standard-2
DEFAULT_DB_CLUSTER_MACHINE_TYPE  = "e2-standard-2"

---

GCP project

• Project: plenary-truck-485623-p7
• Region: us-west3
• Artifact Registry: us-west3-docker.pkg.dev/plenary-truck-485623-p7/knoe-system
• CPU quota: 16 vCPUs (all regions) — 2 clusters × 3 × e2-standard-2 = 12 vCPUs used
• SSD quota: SSD_TOTAL_GB = 300 GB — fully consumed by CNPG; all other PVCs must use standard (pd-standard / HDD)