- add .gitea/workflows/ci.yml with no secrets and no cluster writes - extract static guardrails to scripts/check_manifests.py - add gate1-check STATIC_ONLY=1 for CI without a kubeconfig - add numeric fsGroup to every pod securityContext - document CI and numeric user requirements
This commit is contained in:
1 parent
5b199f8fe3
commit
23ad37699f
11 files changed
+364
-273
No files matched your search
+13
-7
@@ -43,7 +43,7 @@ Findings from `CLUSTER-SMOKE.md`; re-check before trusting this snapshot:
|
||||
unverified UDP.
|
||||
- **Numeric UIDs are required:** a non-numeric image user breaks
|
||||
`runAsNonRoot` on SKE (reproduced with `curlimages/curl`). Every pod in
|
||||
`deploy/k8s/` sets an explicit numeric `runAsUser`/`runAsGroup`.
|
||||
`deploy/k8s/` sets explicit numeric `runAsUser`/`runAsGroup`/`fsGroup`.
|
||||
- **Repo status (2026-11-14 ~05:10 UTC):** all three images now build and pass
|
||||
local manifest-equivalent runtime checks (numeric UID, read-only root, `/tmp`
|
||||
tmpfs). There is no remaining Dockerfile blocker; the human Gitea/Tunnel
|
||||
@@ -167,7 +167,13 @@ want exit 0 while prerequisites are still being prepared.
|
||||
|
||||
Neither target mutates the cluster. `make validate` uses
|
||||
`kubectl apply --dry-run=client`; `make gate1-check` only reads
|
||||
configuration/RBAC/secrets and runs the same dry-run.
|
||||
configuration/RBAC/secrets and runs the same dry-run. CI runs the same static
|
||||
guardrails without a cluster:
|
||||
|
||||
```bash
|
||||
make gate1-check STATIC_ONLY=1
|
||||
make validate
|
||||
```
|
||||
|
||||
## Step 1 — Gitea credentials
|
||||
|
||||
@@ -475,11 +481,11 @@ Each service image must:
|
||||
| api | `git.noelsabia.dev/noelsabia/pulsecast-api:gate1` | 8080 | `65532:65532` | `/api/healthz`, `/api/readyz` |
|
||||
| ml | `git.noelsabia.dev/noelsabia/pulsecast-ml:gate1` | 8000 | `10001:10001` | `/healthz`, `/readyz` |
|
||||
|
||||
The manifests set `runAsUser`/`runAsGroup` explicitly, so the image's named
|
||||
user is irrelevant; the files must be readable by that numeric UID. `api`
|
||||
uses distroless `static:nonroot` (65532); web and ml use 10001. If a Dockerfile
|
||||
genuinely needs another UID, change the manifest and this table together, and
|
||||
keep the value numeric.
|
||||
The manifests set `runAsUser`/`runAsGroup`/`fsGroup` explicitly, so the image's
|
||||
named user is irrelevant; the files must be readable by that numeric UID.
|
||||
`api` uses distroless `static:nonroot` (65532); web and ml use 10001. If a
|
||||
Dockerfile genuinely needs another UID, change the manifest and this table
|
||||
together, and keep the value numeric.
|
||||
|
||||
`api` must read `DATA_DIR` (baked JSON), `FASTAPI_URL`, `PORT`,
|
||||
`CONTROL_USER`, `CONTROL_PASS`, `CONTROL_TOKEN`, `SSE_HEARTBEAT`, and
|
||||
|
||||
Reference in new issue
Block a user