NK-WP-0058-T07: conventions lint, server-side applies, one cluster route
All checks were successful
Bounded-execution contracts / contracts (push) Successful in 1m25s
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

tools/conventions/lint.py (make conventions-lint, contract suite): server-side-apply, one-wait-condition,
one-cluster-route, tool-numbered-receipts, managing-controller (Argo-owned paths from railiance-platform),
with reasoned exceptions. 21 runbook applies made server-side. portal-client-rollout.py (and so
keycape-client.py and the rollout tools) and identity-provisioner-reconcile.py use NK_KUBECONFIG,
default ~/.kube/config-railiance01, without a second kubeconfig or --server override.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 943911@bnt-lap001
Assistant-Session: fc322940-1c8e-4bed-ab39-86cec99f23a0
This commit is contained in:
tegwick 2026-11-06 00:34:00 +01:00
parent 80d280a340
commit cd265b84a4
13 changed files with 226 additions and 28 deletions

View file

@ -54,7 +54,7 @@ kubectl create secret generic net-kingdom-pg-privacyidea-app \
### 3. Deploy the cluster
```bash
kubectl apply -f cluster.yaml
kubectl apply --server-side -f cluster.yaml
```
Wait for cluster to become ready (this provisions PVCs and runs initdb — allow 2–3 minutes):
@ -100,7 +100,7 @@ kubectl create secret generic net-kingdom-pg-backup-s3 \
Apply the updated cluster.yaml, then:
```bash
kubectl apply -f scheduled-backup.yaml
kubectl apply --server-side -f scheduled-backup.yaml
```
### 6. Run the restore drill