sirius/gcloud-lab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
gcloud-lab/apps/base/customer1/siriusdevops-db/kustomization.yaml

16 lines
464 B
YAML
Raw Normal View History

feat: add siriusdevops CNPG cluster + waitlist API K8s manifests (#112) - New CNPG PostgreSQL cluster (siriusdevops-pgdb) in customer1 namespace - Single-instance, 20Gi storage, GCS backups to siriusdevops-backups/ - Waitlist database definition (waitlist-db.yaml) - Scheduled backup manifest - Waitlist API deployment, service, HTTPRoute, and Telegram secret placeholder - Kustomization wiring for both siriusdevops-db and waitlist-api
2026-05-14 19:24:33 -04:00
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
resources:
- pg-cluster-siriusdevops.yaml
- waitlist-db-credentials.yaml
- waitlist-db.yaml
- siriusdevops-scheduled-backup.yaml
feat: migrate all trading-platform services from hermes-pgdb to siriusdevops-pgdb - Add 'trading' managed role to siriusdevops-pgdb cluster - Move trading-db-credentials from hermes-db to siriusdevops-db - Create trading-data-db.yaml (Database kind) pointing to siriusdevops-pgdb - Update DB_HOST in all 4 trading-platform configmaps to siriusdevops-pgdb-rw - Remove trading-data-db.yaml and trading-db-credentials.yaml from hermes-db - Update siriusdevops-db kustomization.yaml to include new resources
2026-05-25 07:55:15 +00:00
# Trading dashboard DB
feat(customer1): add trading_dashboard database to siriusdevops-pgdb CNPG cluster - Add trading_dashboard role + Database CR on siriusdevops-pgdb - Create SOPS-encrypted credentials secret (template) - Update trade-dashboard to use the new dedicated DB - New host: siriusdevops-pgdb-rw - New database: trading_dashboard - New credentials secret
2026-05-24 20:02:20 +00:00
- trading-dashboard-db-credentials.yaml
feat: migrate all trading-platform services from hermes-pgdb to siriusdevops-pgdb - Add 'trading' managed role to siriusdevops-pgdb cluster - Move trading-db-credentials from hermes-db to siriusdevops-db - Create trading-data-db.yaml (Database kind) pointing to siriusdevops-pgdb - Update DB_HOST in all 4 trading-platform configmaps to siriusdevops-pgdb-rw - Remove trading-data-db.yaml and trading-db-credentials.yaml from hermes-db - Update siriusdevops-db kustomization.yaml to include new resources
2026-05-25 07:55:15 +00:00
# Trading platform DB (migrated from hermes-pgdb)
- trading-db-credentials.yaml
- trading-data-db.yaml
split Strimzi operator into separate kustomization for Flux dependsOn Flux dry-run fails when CRDs are in the same kustomization as resources that reference them - CRDs need to exist before validation. Two kustomizations now: strimzi/ - Strimzi 1.0.0 CRDs + operator siriusdevops-db - DBs, Kafka CR (depends on strimzi CRDs) Wire them in Flux: Kustomization 'siriusdevops-strimzi' -> path: strimzi/ Kustomization 'siriusdevops-db' -> path: siriusdevops-db/ dependsOn: [{name: siriusdevops-strimzi}]
2026-05-26 01:09:56 +00:00
# Kafka cluster (depends on strimzi/ kustomization for CRDs)
replace manual Kafka StatefulSet with Strimzi operator CR Remove hand-rolled KRaft StatefulSet that kept failing (mount conflicts, advertised.listeners issues). Replace with a single Strimzi Kafka CR. Strimzi handles: - KRaft setup, storage, scaling - Broker config & advertised listeners (auto-resolved) - Topic Operator for proper topic lifecycle - Bootstrap service at trading-kafka-kafka-bootstrap.customer1.svc.cluster.local:9092 Requires Strimzi 1.0.0 operator installed in the cluster first: kubectl apply -f https://strimzi.io/install/latest?namespace=customer1 -n customer1
2026-05-26 00:37:36 +00:00
- trading-kafka.yaml
Reference in a new issue Copy permalink