ci: add cluster-free manifest validation
infra-ci / manifests (push) Failing after 3s

- 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:
Noel Sabia committed 2026-11-14 05:49:06 +01:00
1 parent 5b199f8fe3
commit 23ad37699f
11 files changed
+364 -273

No files matched your search

+40
View File
@@ -0,0 +1,40 @@
name: infra-ci
on:
push:
branches:
- main
- "feat/**"
pull_request:
jobs:
manifests:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Install validation dependency
run: |
python3 -m pip install --user pyyaml \
|| python3 -m pip install --break-system-packages pyyaml
# No kubeconfig and no cluster mutation here. This is the same guardrail
# set used locally: namespace-only kinds, numeric UIDs, securityContext,
# probes, resources, env/Secret references, image tags, Service types.
- name: Static manifest guardrails
run: make gate1-check STATIC_ONLY=1
# Falls back to YAML parsing when kubectl or a cluster is unavailable.
- name: YAML parse or client dry-run
run: make validate
# The brief's client dry-run, only when this runner actually has a
# reachable kubeconfig. No Secrets are configured in CI.
- name: kubectl client dry-run when a cluster is configured
run: |
if kubectl get --raw=/readyz >/dev/null 2>&1; then
kubectl apply --dry-run=client -f deploy/k8s
else
echo "No reachable kubeconfig on this runner; static guardrails already passed."
fi