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.
19 lines
590 B
Markdown
19 lines
590 B
Markdown
# 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:
|
|
|
|
```text
|
|
k8s/railiance/
|
|
```
|
|
|
|
Do not commit Kubernetes Secret values, ArgoCD repository credentials, OpenBao
|
|
tokens, deploy keys, or API keys here.
|
|
|