gcloud-lab/apps/base/customer1/trading-platform/dashboard/service.yaml

apiVersion: v1
kind: Service
metadata:
  name: trading-dashboard-svc
  namespace: customer1
  annotations:
    tailscale.com/expose: "true"
    tailscale.com/hostname: "trading-dashboard"
    tailscale.com/tags: "tag:k8s-operator"
    tailscale.com/ports: "http:3000"
spec:
  selector:
    app: trading-dashboard
  ports:
    - port: 3000
      targetPort: 3000
      name: http
  type: ClusterIP
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: v1`
			`kind: Service`
			`metadata:`
			`name: trading-dashboard-svc`
			`namespace: customer1`
			`annotations:`
			`tailscale.com/expose: "true"`
			`tailscale.com/hostname: "trading-dashboard"`
			`tailscale.com/tags: "tag:k8s-operator"`
fix(dashboard): add explicit tailscale.com/ports: "http:3000" annotation Matches the exact annotation pattern used for other tailnet services (Grafana, trade-dashboard, hermes-webui, etc.). This ensures the Tailscale operator correctly maps the exposed port after the 3000 change. 2026-05-25 06:05:51 +00:00			`tailscale.com/ports: "http:3000"`
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			`spec:`
			`selector:`
			`app: trading-dashboard`
			`ports:`
fix(dashboard): add explicit tailscale.com/ports: "http:3000" annotation Matches the exact annotation pattern used for other tailnet services (Grafana, trade-dashboard, hermes-webui, etc.). This ensures the Tailscale operator correctly maps the exposed port after the 3000 change. 2026-05-25 06:05:51 +00:00			`- port: 3000`
fix(dashboard): align port to 3000 and probes to root path - containerPort: 3000 (matches Next.js default + Dockerfile ENV PORT=3000) - All probes (startup/liveness/readiness): path (Next.js serves root when ready) - Service targetPort: 3000 Fixes 'not ready' and 'can't reach it' (previous mismatch with 8000 + /api/health which didn't exist). Live manifests updated (source of truth). 2026-05-25 05:55:21 +00:00			`targetPort: 3000`
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			`name: http`
			`type: ClusterIP`