Publish cluster resource evidence and gate ThreePhoenix
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
parent
bfc991258d
commit
ea0452b9a9
11 changed files with 2768 additions and 23 deletions
18
SCOPE.md
18
SCOPE.md
|
|
@ -90,8 +90,8 @@ future `rail-kubernetes` repo and must not be treated as long-term S2 scope.
|
|||
`platform-pg`, `state-hub-db`, `target-revenue-pg`, `user-engine-pg`
|
||||
- No monitoring stack is deployed on either cluster — observability is Q2 and
|
||||
homed in `railiance-telemetry`, which is seeded but not implemented
|
||||
- k3s API access is source-restricted by UFW; see `railiance-infra`
|
||||
`RAIL-HO-WP-0009`
|
||||
- k3s API access is tunnel-only on Railiance01; see `railiance-infra`
|
||||
`RAIL-HO-WP-0009` and ADR-005. It is not a public/source-allowlisted surface.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -130,15 +130,15 @@ future `rail-kubernetes` repo and must not be treated as long-term S2 scope.
|
|||
```capability
|
||||
type: infrastructure
|
||||
title: Kubernetes cluster provisioning (k3s)
|
||||
description: Install and configure a production k3s cluster including Helm, ingress controller, CNI plugin, and kubeconfig management on Railiance servers.
|
||||
description: Install and configure a production k3s cluster including Helm, Traefik ingress, networking, and kubeconfig management on Railiance servers.
|
||||
keywords: [kubernetes, k3s, cluster, helm, ingress, cni, k8s, provisioning]
|
||||
```
|
||||
|
||||
```capability
|
||||
type: infrastructure
|
||||
title: Cluster operators and addon management
|
||||
description: Deploy and manage cluster-wide operators and addons (cert-manager, CloudNative PG operator, ArgoCD, nginx ingress) on the running Railiance Kubernetes cluster.
|
||||
keywords: [operator, addon, cert-manager, cnpg, argocd, admission, kubernetes, cluster]
|
||||
description: Deploy and manage cluster-wide operators and addons, including cert-manager, CloudNative PG, Traefik, Knative Serving, External Secrets, and OpenBao integration, on the running Kubernetes cluster.
|
||||
keywords: [operator, addon, cert-manager, cnpg, traefik, knative, admission, kubernetes, cluster]
|
||||
```
|
||||
|
||||
```capability
|
||||
|
|
@ -152,10 +152,10 @@ keywords: [backup, restore, age, encryption, k3s, state, helm, kubeconfig, disas
|
|||
|
||||
## Notes
|
||||
|
||||
Runs on COULOMBCORE (92.205.130.254). State Hub access via ops-bridge reverse
|
||||
tunnel - `bridge up state-hub-coulombcore` from the workstation (see ADR-004).
|
||||
Gitea Helm values were migrated to S5 (railiance-apps) in RAIL-HO-WP-0004-T06 -
|
||||
boundary violation resolved.
|
||||
The live primary is Railiance01 (`92.205.62.239`). CoulombCore
|
||||
(`92.205.130.254`) is the older frozen cluster and remains a legacy recovery
|
||||
surface, not the default deployment target. State Hub and Kubernetes API access
|
||||
use the corresponding ops-bridge tunnels (see ADR-004/ADR-005).
|
||||
|
||||
`bin/railiance` lifecycle subcommands, `railiance/app.toml`, and overlay/wrapper
|
||||
scaffolding stay in this repo only as a migration bridge. They are not the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue