Celes Renata
ebea70573b
- Repository structure for all services, infra, lakehouse, dashboards - K8s manifests targeting stonks-oracle namespace with GHCR images - Ingress via Traefik with ca-issuer TLS for internal services - ConfigMap wired to existing cluster services (pg, redis, minio, ollama) - GitHub Actions workflow for lint, test, multi-service container builds - Dockerfile with build-arg CMD per service - Makefile for local build/push/deploy - Steering rules for TDD workflow, K8s conventions, project context - Agent hooks for lint-on-save, test-on-save, k8s-validate, phase-commit - Ruff linter config, all lint issues fixed - 14 passing tests for schemas, config, redis keys - PostgreSQL migrations, Trino catalogs, Superset config, MinIO lifecycle
17 lines
512 B
Markdown
17 lines
512 B
Markdown
---
|
|
name: Validate K8s Manifests
|
|
description: Validate Kubernetes YAML when manifest files are saved
|
|
version: "1.0"
|
|
trigger:
|
|
type: onSave
|
|
filePattern: "infra/k8s/**/*.yaml"
|
|
---
|
|
|
|
When a Kubernetes manifest YAML file is saved:
|
|
|
|
1. Parse the YAML to check for syntax errors
|
|
2. Verify required fields exist (apiVersion, kind, metadata)
|
|
3. Check that namespace is set to `stonks-oracle` for application resources
|
|
4. Verify image references point to `ghcr.io/celesrenata/stonks-oracle/`
|
|
5. Report any issues found
|