Files
0pt/deploy/k8s
siax-bot 5a6d5618e0
CI (SIAX Cloud) / sonar (pull_request) Skipped
masterplan-lock / check (pull_request) Successful in 5s
CI (SIAX Cloud) / Component conformance (blocking) (pull_request) Successful in 8s
CI (SIAX Cloud) / security (pull_request) Successful in 15s
security / scan (pull_request) Successful in 39s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m8s
CI (SIAX Cloud) / quality (pull_request) Successful in 1m44s
fix(ci): clear 0pt security/scan baseline (pinned tooling, non-root runtime)
2026-11-20 20:20:57 +01:00
..

Kubernetes manifests — reference only, NOT the deploy path

BACKLOG P6 (CD-23). 0pt's actual deploy target is Coolify (ADR-0001, siax.config.json), which runs the committed Dockerfile directly — it does not consume Kubernetes manifests. deploy/k8s/deployment.yaml in this directory is a reference example only, for the scenario where a future SIAX Cloud node runs k8s instead of/alongside Coolify. It is not applied by any CI/CD path in this repo, and nothing in .gitea/workflows/ references it.

Do not kubectl apply this against a real cluster without first replacing the placeholder image reference and reviewing resource limits against actual measured usage (none exists yet — 0pt has no live traffic history to size against, see BACKLOG P0-2/D5).