coulomb/railiance-platform
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/argocd/applications
History
tegwick 60447e8b0a
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 5s
Details
Point issue-core ArgoCD Application at Forgejo Git source 
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
..
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 Add ESO OpenBao GitOps add-ons 2026-06-25 20:08:36 +02:00
README.md Add ArgoCD GitOps bootstrap contract for railiance01 2026-06-19 21:05:12 +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.