coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/argocd/applications
History
Exact
codex 2cb3a24d6d Add ArgoCD Application for target-revenue Trust Service 
WP-0011: sync coulomb/target-revenue path k8s/railiance into namespace
target-revenue (revenue.coulomb.social). Requires image, OpenBao secrets,
and DNS before a healthy sync — see target-revenue docs/deployment.md.
2026-08-05 16:41:00 +02:00
..
external-secrets.application.yaml Add ESO OpenBao GitOps add-ons 2026-06-25 20:08:36 +02:00
issue-core.application.yaml Point issue-core ArgoCD Application at Forgejo Git source 2026-07-08 15:21:00 +02:00
openbao-secretstore.application.yaml Repoint ArgoCD GitOps to Forgejo (RAIL-HO-WP-0005 T11) 2026-07-08 15:35:28 +02:00
README.md Add ArgoCD GitOps bootstrap contract for railiance01 2026-06-19 21:05:12 +02:00
target-revenue.application.yaml Add ArgoCD Application for target-revenue Trust Service 2026-08-05 16:41:00 +02:00

README.md

Railiance ArgoCD Tenant Applications

This directory is synced by the railiance-apps-root ArgoCD Application.

Tenant teams author a thin ArgoCD Application manifest against the contract in docs/argocd-gitops.md. Platform review merges that manifest here after checking namespace, repository, sync policy, and secret-delivery shape.

Workload manifests stay in the owning tenant repo. The default source path for tenant workloads is:

k8s/railiance/

Do not commit Kubernetes Secret values, ArgoCD repository credentials, OpenBao tokens, deploy keys, or API keys here.