tegwick df7225dd3e

CI Smoke / host-smoke (push) Successful in 0s

Details

CI Smoke / container-smoke (push) Successful in 5s

Details

RAILIANCE-WP-0012/0013/0014: Core Hub S5 release, CNPG observability, and follow-up workplans

Deliver the inbox-suggestion implementation from WP-0012: Core Hub Helm chart
and Makefile targets, CNPG backup status tooling, and updated backup handoff
docs. Archive the finished WP-0012 workplan and register ready follow-ups
WP-0013 (CNPG backup wiring + restore drill) and WP-0014 (Core Hub Helm
cutover and vergabe-teilnahme image refresh).

2026-07-10 15:14:20 +02:00

3.2 KiB

Raw Blame History

Core Hub on railiance01

hub.coulomb.social serves Core Hub in production. This repo owns the S5 Helm release path; Core Hub owns the application image, migrations, and API behavior.

Hosts and release surface

Server	IP	Role
Railiance01	`92.205.62.239`	Production k3s; deploy S5 apps here

Item	Production	Staging
Namespace	`core-hub`	`core-hub-staging`
Helm release	`core-hub`	`core-hub`
Chart	`charts/core-hub`	`charts/core-hub`
Values	`helm/core-hub-values.yaml`	`helm/core-hub-staging-values.yaml`
Image	`forgejo.coulomb.social/coulomb/core-hub:<tag>`	same
Runtime Secret	`core-hub-prod-env`	`core-hub-staging-env`
Public host	`hub.coulomb.social`	cluster-local / port-forward

Secret custody

Do not commit decrypted secrets. Runtime secrets are operator-owned and should reference OpenBao or approved platform custody paths:

Secret key	Purpose
`CORE_HUB_DATABASE_URL`	Async SQLAlchemy URL for the environment database
`CORE_HUB_API_TOKEN`	Operator token for protected API smokes

CORE_HUB_AUTO_CREATE_TABLES must remain 0 in cluster environments. Alembic is the only schema path.

Deploy

Use the Railiance01 kubeconfig. The Makefile defaults to ~/.kube/config-hosteurope and fails fast when it is missing.

make core-hub-render-baseline
CORE_HUB_IMAGE_TAG=<sha> make check-core-hub-image
CORE_HUB_IMAGE_TAG=<sha> make core-hub-dry-run
CORE_HUB_IMAGE_TAG=<sha> make core-hub-server-dry-run
CORE_HUB_IMAGE_TAG=<sha> make core-hub-migrate
CORE_HUB_IMAGE_TAG=<sha> make core-hub-deploy
make core-hub-status
make core-hub-smoke

Production deploys require an explicit image tag. The checked-in values file carries a render baseline only.

Staging follows the same pattern with core-hub-staging-* targets and helm/core-hub-staging-values.yaml.

Ingress cutover

The chart can render the production ingress for hub.coulomb.social. During an initial cutover from the legacy Inter-Hub ingress, delete the conflicting inter-hub ingress before applying the Core Hub ingress. See core-hub/k8s/railiance-production/README.md for the historical flip sequence.

Migration boundary

make core-hub-migrate renders and applies a one-off Job using the same image tag as deploy. Wait for Job completion before rolling out a schema-dependent image change.

Smoke gate

make core-hub-smoke checks:

/healthz and /readyz
/api/v2/openapi.json resource coverage
public /api/v2/widget-types
protected /api/v2/hubs, /api/v2/widgets, /api/v2/hub-registry

For operator-authenticated smokes and activity-core sink proof, use the Core Hub service-repo targets documented in core-hub/docs/deployment/staging-profile.md.

Rollback

Scale the Core Hub Deployment to zero or roll back to the last known good tag.
Re-apply the legacy Inter-Hub ingress if public routing must return to the Haskell service during stabilization.
Do not delete legacy Inter-Hub runtime secrets during rollback.

the-custodian/docs/core-hub-helixforge-build-alignment.md
core-hub/docs/deployment/staging-profile.md
docs/inter-hub-on-railiance01.md (retired Inter-Hub path)

3.2 KiB Raw Blame History