From 1d68639225f1bba8528ffdfdf5470edd7f21f2d0 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 24 May 2026 17:17:37 +0200 Subject: [PATCH] Align KeyCape image namespace with deployment --- .gitea/workflows/image.yaml | 2 +- Makefile | 2 +- README.md | 4 ++-- workplans/KEY-WP-0002-container-image-gitea.md | 14 +++++++------- 4 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.gitea/workflows/image.yaml b/.gitea/workflows/image.yaml index cdb288a..df80050 100644 --- a/.gitea/workflows/image.yaml +++ b/.gitea/workflows/image.yaml @@ -9,7 +9,7 @@ on: env: REGISTRY: 92.205.130.254:32166 - IMAGE_NAME: netkingdom/key-cape + IMAGE_NAME: coulomb/key-cape jobs: build-and-push: diff --git a/Makefile b/Makefile index 370923f..d0ec289 100644 --- a/Makefile +++ b/Makefile @@ -1,5 +1,5 @@ IMAGE_REGISTRY ?= 92.205.130.254:32166 -IMAGE_REPO ?= netkingdom/key-cape +IMAGE_REPO ?= coulomb/key-cape IMAGE_TAG ?= latest IMAGE := $(IMAGE_REGISTRY)/$(IMAGE_REPO):$(IMAGE_TAG) diff --git a/README.md b/README.md index 27980b8..8fd2f33 100644 --- a/README.md +++ b/README.md @@ -202,12 +202,12 @@ wiki/ # Specifications The KeyCape image is published to the Gitea OCI registry on CoulombCore. **Registry:** `92.205.130.254:32166` -**Image:** `92.205.130.254:32166/netkingdom/key-cape` +**Image:** `92.205.130.254:32166/coulomb/key-cape` ### Pull ```bash -docker pull 92.205.130.254:32166/netkingdom/key-cape:latest +docker pull 92.205.130.254:32166/coulomb/key-cape:latest ``` The registry runs over plain HTTP. Configure Docker to allow it: diff --git a/workplans/KEY-WP-0002-container-image-gitea.md b/workplans/KEY-WP-0002-container-image-gitea.md index e6350ed..14de695 100644 --- a/workplans/KEY-WP-0002-container-image-gitea.md +++ b/workplans/KEY-WP-0002-container-image-gitea.md @@ -32,7 +32,7 @@ registry on CoulombCore (`92.205.130.254:32166`), triggered automatically on every merge to `main` and on semver tags (`v*`). **Gitea OCI registry endpoint:** `92.205.130.254:32166` -**Image name:** `92.205.130.254:32166/netkingdom/key-cape` +**Image name:** `92.205.130.254:32166/coulomb/key-cape` > **Why Gitea, not GHCR?** > The net-kingdom cluster is self-hosted. Keeping images in Gitea (also @@ -67,7 +67,7 @@ the push target runs. ```makefile IMAGE_REGISTRY ?= 92.205.130.254:32166 -IMAGE_REPO ?= netkingdom/key-cape +IMAGE_REPO ?= coulomb/key-cape IMAGE_TAG ?= latest IMAGE := $(IMAGE_REGISTRY)/$(IMAGE_REPO):$(IMAGE_TAG) @@ -122,7 +122,7 @@ state_hub_task_id: "749472fc-edb9-4948-9ebc-58d5f38327ee" Add `image`, `push`, and `image-tag` targets to `Makefile` with `IMAGE_REGISTRY`, `IMAGE_REPO`, `IMAGE_TAG` variables defaulting to the -Gitea endpoint and `netkingdom/key-cape:latest`. +Gitea endpoint and `coulomb/key-cape:latest`. Gate: `make image` builds successfully locally; `IMAGE_TAG=dev make image` produces a differently-tagged image. @@ -163,7 +163,7 @@ state_hub_task_id: "2dde67f9-944f-418d-a2e9-7367bc556425" On CoulombCore, create/update `/etc/rancher/k3s/registries.yaml` to add the Gitea NodePort as an HTTP mirror. Restart k3s (or send SIGHUP) and -verify `crictl pull 92.205.130.254:32166/netkingdom/key-cape:latest` works. +verify `crictl pull 92.205.130.254:32166/coulomb/key-cape:latest` works. Gate: image pull from within the cluster succeeds without TLS errors. @@ -209,10 +209,10 @@ IMAGE_TAG=dev make push Then verify the image is pullable from CoulombCore: ```bash # on CoulombCore -crictl pull 92.205.130.254:32166/netkingdom/key-cape:dev +crictl pull 92.205.130.254:32166/coulomb/key-cape:dev ``` -Gate: pull succeeds; image is listed in Gitea → Packages → netkingdom/key-cape. +Gate: pull succeeds; image is listed in Gitea -> Packages -> coulomb/key-cape. --- @@ -227,7 +227,7 @@ state_hub_task_id: "946cd34d-94da-4fa9-a781-ed36f6c827a3" Add a "Container Image" section to `README.md` documenting: - Registry URL and image name -- How to pull (`docker pull 92.205.130.254:32166/netkingdom/key-cape:latest`) +- How to pull (`docker pull 92.205.130.254:32166/coulomb/key-cape:latest`) - How to build and push locally (Makefile targets) - CI secrets required for the Actions workflow