ci: run manifest checks on the Gitea runner
infra-ci / manifests (push) Successful in 8s
infra-ci / manifests (pull_request) Successful in 8s

The node:20-bookworm runner has python3 but no pip, so the PyYAML install failed before any check ran. Install python3-yaml with apt instead, remove the duplicate cluster-only kubectl step, and keep the two cluster-free Make targets.

Also remove the stale v1.0/pending-review claims, drop the old api.pulse hostname, and move the deploy status below the runbook.
This commit is contained in:
Noel Sabia committed 2026-11-14 09:13:27 +01:00
1 parent bd3176bef0
commit e8e048866c
10 files changed
+102 -104

No files matched your search

+7 -15
View File
@@ -14,27 +14,19 @@ jobs:
- name: Checkout
uses: actions/checkout@v4
# The runner image has python3 but neither pip nor PyYAML.
- name: Install validation dependency
run: |
python3 -m pip install --user pyyaml \
|| python3 -m pip install --break-system-packages pyyaml
if ! python3 -c 'import yaml' 2>/dev/null; then
apt-get update -qq
apt-get install -y -qq python3-yaml
fi
# 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.
# Cluster-free guardrails: namespace-only kinds, numeric UIDs,
# securityContext, probes, resources, env/Secret refs, image tags, Services.
- 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