gcloud-lab/apps/base/customer1/trading-platform/secrets/kustomization.yaml

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

resources:
  - trading-secrets.yaml
  - execute-service-jwt-secret.yaml
  - solana-api-keys.yaml
feat: add trading-platform K8s manifests for customer1 - Scaffold trading-platform under apps/base/customer1/trading-platform/ - Add 4 microservice deployments: data-service, execute-service, news-service, dashboard - Add ConfigMaps with DB/Kafka/Redis connection configs - Add HTTPRoutes via Gateway API (external-http-gateway) - Add NetworkPolicies for inter-service and DB/Kafka/Redis egress - Add SOPS-encrypted secrets (age key) - Add Kafka (KRaft) and Redis infrastructure to hermes-db/ - Update root and staging kustomizations All containers: non-root, readOnlyRootFilesystem, resource limits, health probes Images: ghcr.io/sirius0xdev/trading-{service}:latest 2026-05-21 04:08:58 +00:00			`apiVersion: kustomize.config.k8s.io/v1beta1`
			`kind: Kustomization`

			`resources:`
			`- trading-secrets.yaml`
fix: wire JWT_SECRET_KEY in live kustomize path Previous PR #139 added the secret to trading-platform/deploy/k8s/base/ but the live cluster uses apps/base/customer1/trading-platform/ kustomize. - Create execute-service-jwt-secret.yaml (SOPS encrypted) in secrets/ - Add to secrets/ kustomization.yaml resources - Wire JWT_SECRET_KEY env var in execute-service deployment - Points to execute-service-jwt-secret via secretKeyRef 2026-05-25 01:53:19 +00:00			`- execute-service-jwt-secret.yaml`
fix(secrets): split Solana API keys into separate SOPS file - Remove helius/jupiter placeholders from trading-secrets.yaml - Create new solana-api-keys.yaml with helius-api-key and jupiter-api-key - Update kustomization.yaml to include solana-api-keys.yaml Convention: each secret group gets its own SOPS-encrypted file instead of adding new keys to an already encrypted file. 2026-05-27 04:35:47 +00:00			`- solana-api-keys.yaml`