coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add interim coulombcore OpenBao token bootstrap for Forgejo mailer ESO

Browse source 
Document two OpenBao instances and add forgejo-openbao-eso-token-apply for
ClusterSecretStore openbao-forgejo on bao.coulomb.social.
This commit is contained in:
tegwick 2026-07-07 14:35:49 +02:00
parent d5bb4f66f2
commit 844a3503bb
3 changed files with 56 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/forgejo-on-railiance01.md
View file

@ -113,13 +113,16 @@ Mailbox password is stored in **OpenBao** and delivered by External Secrets:
| ExternalSecret | `manifests/forgejo-mailer-externalsecret.yaml` |
| Helm consumption | `gitea.additionalConfigFromEnvs` → `GITEA__mailer__PASSWD` |
**OpenBao note:** `https://bao.coulomb.social` is coulombcore (live, unsealed).
The in-cluster `openbao.openbao.svc` pod on railiance01 is a separate instance
that is **not initialized** yet — ESO uses the coulombcore endpoint interim
until Wave 7 migrates OpenBao custody to railiance01.
Bootstrap (railiance01):
```bash
cd ~/railiance-platform
KUBECONFIG=~/.kube/config-hosteurope make openbao-configure-external-secrets-forgejo
cd ~/railiance-apps
KUBECONFIG=~/.kube/config-hosteurope make forgejo-openbao-eso-token-apply
KUBECONFIG=~/.kube/config-hosteurope make forgejo-mailer-es-deploy
KUBECONFIG=~/.kube/config-hosteurope make forgejo-mailer-es-status # expect SecretSynced
KUBECONFIG=~/.kube/config-hosteurope make forgejo-deploy