railiance-apps/workplans/RAILIANCE-WP-0014-core-hub-helm-cutover-vergabe-refresh.md
tegwick e9ee577d03
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 20s
WP-0014: Helm adopt and deploy Core Hub on CoulombCore; backup auth tooling
Adopt live Core Hub resources, align prod ConfigMap naming, default production
image registry to gitea, and install Helm release core-hub rev 1 (smoke passed).
Add apps-pg-backup and check-backup-lane-auth targets; document OIDC login
requirement now that OpenBao is unsealed.
2026-07-10 21:47:14 +02:00

92 lines
No EOL
2.8 KiB
Markdown

---
id: RAILIANCE-WP-0014
type: workplan
title: "Core Hub Helm cutover and vergabe-teilnahme image refresh"
domain: financials
repo: railiance-apps
status: active
owner: codex
topic_slug: railiance
created: "2026-07-10"
updated: "2026-07-10"
state_hub_workstream_id: "780c8d1d-ea75-479e-9733-10b518dde242"
---
# Core Hub Helm cutover and vergabe-teilnahme image refresh
Follow-up to `RAILIANCE-WP-0012` and custodian inbox `3ced85c7`. The S5 Helm
chart, values, Makefile targets, and runbook exist; the live cluster may still
run Core Hub from `core-hub/k8s/railiance-production/` manifests.
Separately, the 2026-07-10 delivery-lane snapshot shows `vergabe-teilnahme`
deployed at `f95de14` while the source repo head is `1061f3e` (14-commit drift).
Production-touching deploy steps require explicit image tags and operator
approval. Do not store secrets in workplans.
## Core Hub server dry-run on CoulombCore
```task
id: RAILIANCE-WP-0014-T01
status: done
priority: high
state_hub_task_id: "b9dea9f3-f0c0-41c1-b9c4-ec4c44d43d55"
```
CoulombCore production cluster confirmed. `core-hub-server-dry-run` passed after
`make core-hub-helm-adopt` and configMap name alignment (`core-hub-prod-runtime`).
Live image `gitea.coulomb.social/coulomb/core-hub:a33191a` verified.
## Adopt Helm-managed Core Hub release
```task
id: RAILIANCE-WP-0014-T02
status: done
priority: high
state_hub_task_id: "0e591104-0123-4e4a-84ff-5deb435e8441"
```
`CORE_HUB_IMAGE_TAG=a33191a make core-hub-deploy` installed Helm release
`core-hub` revision 1 on CoulombCore. Resources carry Helm ownership metadata.
Service-repo `k8s/railiance-production/` path is now superseded for operations.
## Verify Core Hub post-cutover smoke
```task
id: RAILIANCE-WP-0014-T03
status: done
priority: high
state_hub_task_id: "eca3ce8b-68a8-44d0-90c7-2cdefa482200"
```
Post-deploy `make core-hub-status` and `make core-hub-smoke` passed on
`https://hub.coulomb.social` after Helm rollout (2026-07-10).
## Refresh vergabe-teilnahme production image
```task
id: RAILIANCE-WP-0014-T04
status: todo
priority: medium
state_hub_task_id: "d547f68d-52ec-4ff1-952b-ec70c834e0d3"
```
Identify the current published image tag for `vergabe-teilnahme` in the Forgejo
registry, verify the manifest with `tools/check-oci-image.sh`, run
`vergabe-dry-run` and `vergabe-server-dry-run` if available, then deploy with an
explicit tag. Close the 14-commit drift noted in the delivery-lane evidence.
## Post-deploy vergabe smoke and runbook evidence
```task
id: RAILIANCE-WP-0014-T05
status: wait
priority: medium
state_hub_task_id: "4eaaa345-4252-46c1-bd8a-49d654ec48f4"
```
After deploy, run `make vergabe-status`, migrations if required, and HTTPS smoke
against `vergabe-teilnahme.whywhynot.de`. Update `docs/vergabe-teilnahme.md`
with the deployed tag, date, and smoke result (non-secret).
Blocked on: `RAILIANCE-WP-0014-T04`.