coulomb/net-kingdom
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(workplan): NK-WP-0003-T07 blocked — awaiting GHCR image from key-cape

Browse Source 
Deployment applied; pod in ImagePullBackOff. Secrets already correct.
Capability request 0e0aefd7 filed; key-cape must publish ghcr.io image.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-03-21 22:24:32 +00:00
parent f2f07871eb
commit d0629e7f20
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
workplans/NK-WP-0003-keycape-privacyidea-cluster-deployment.md
View File

@@ -214,9 +214,17 @@ Verify: `bash sso-mfa/k8s/verify-t05.sh` (covers LLDAP + Authelia together)
```task
id: NK-WP-0003-T07
status: todo
status: blocked
priority: high
state_hub_task_id: "496a97c9-3e2a-486e-ba62-18449868c6cf"
note: Blocked 2026-03-21 — keycape:v0.1 image cannot be built on the k3s node (no Docker/Go).
Deployment applied; pod stuck in ImagePullBackOff.
Secrets keycape-config + keycape-pi-token already in cluster (both correct, real PI token).
Capability request filed: hub ID 0e0aefd7 (routed to railiance, direct msg sent to key-cape).
key-cape repo must deliver:
1. .github/workflows/publish.yml — build+push to ghcr.io/<owner>/keycape:v0.1 on main
2. Update net-kingdom/sso-mfa/k8s/keycape/deployment.yaml image: to GHCR reference
Once image is published: kubectl rollout restart deployment/keycape -n sso
```
Deploy KeyCape into the `sso` namespace.