Commit graph

10 commits

Author SHA1 Message Date
6abf6b56a0 Fix openbao-secretstore ArgoCD health: coulombcore scope only
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Remove interim ClusterSecretStores (forgejo, activity-core, reuse) from
coulombcore ArgoCD kustomization. Those stores target railiance01 namespaces
and are bootstrapped via railiance-apps/activity-core Make targets.
2026-07-08 15:41:04 +02:00
6076d57218 Repoint ArgoCD GitOps to Forgejo (RAIL-HO-WP-0005 T11)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Switch bootstrap AppProjects, root application, openbao-secretstore, and
repository template URLs from gitea.coulomb.social to forgejo.coulomb.social.
2026-07-08 15:35:28 +02:00
60447e8b0a Point issue-core ArgoCD Application at Forgejo Git source
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 5s
ArgoCD was still tracking gitea.coulomb.social, which lags Forgejo after the
registry migration. Sync issue-core workload manifests from forgejo.coulomb.social
so backend ConfigMap updates land on CoulombCore.

Also allow forgejo.coulomb.social in railiance-tenants AppProject sourceRepos.
2026-07-08 15:21:00 +02:00
e36694648a Support activity-core ISSUE_CORE_API_KEY ExternalSecret on railiance01
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 3s
Switch openbao-activity-core ClusterSecretStore to interim coulombcore
token auth like forgejo/reuse, broaden the activity-core ESO policy to
include the shared issue-core runtime path, and document ESO-managed rotation.
2026-07-08 00:04:59 +02:00
d64fa814b1 Activate reuse-surface runtime secrets OpenBao lane (CCR-2026-0005)
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
CI Smoke / container-smoke (push) Waiting to run
Approve CCR-2026-0005, apply delegated OpenBao metadata, seed the KV path,
verify ExternalSecret delivery on Railiance01, and complete RAILIANCE-WP-0011-T02.
2026-07-07 22:34:34 +02:00
f428940da8 Point Forgejo ClusterSecretStore at live coulombcore OpenBao
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Use https://bao.coulomb.social with token auth until railiance01 OpenBao is
bootstrapped; the in-cluster railiance01 instance is not initialized.
2026-07-07 14:35:46 +02:00
0941d6e8f9 Add OpenBao External Secrets lane for Forgejo mailer on railiance01
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 6s
Introduce external-secrets-forgejo policy/role, ClusterSecretStore
openbao-forgejo (forgejo namespace), and make openbao-configure-external-secrets-forgejo.
2026-07-07 14:30:02 +02:00
a95236d2e5 Add credential-change delegated applier flow 2026-07-01 20:07:26 +02:00
693dc71833 Add ESO OpenBao GitOps add-ons 2026-06-25 20:08:36 +02:00
64d7c18c3f Add ArgoCD GitOps bootstrap contract for railiance01
Define platform-owned AppProjects, root app-of-apps, repository registration
templates, and tenant onboarding docs so issue-core can deploy via ArgoCD.
Ignore encrypted repository secrets locally and cross-link OpenBao delivery
guidance with the new GitOps contract.
2026-06-19 21:05:12 +02:00