tegwick
b7fb7b226f
- coulomb-social: requests 100m/256Mi -> 15m/176Mi (limits unchanged)
- reuse-surface: main 100m/256Mi -> 5m/64Mi, landing 10m/32Mi -> 5m/16Mi
- vergabe-demo-company: memory request 256Mi -> 512Mi, CPU 60m kept
- inter-hub (retired, CORE-WP-0007): delete chart, values, Make targets,
smoke script and production deploy workflow; release to be uninstalled
Full renders vs live: resources only, except the vergabe release-unit label
from 64530e1 not yet on its Service and PVCs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
117 lines
3.8 KiB
Markdown
117 lines
3.8 KiB
Markdown
---
|
|
id: capability.railiance.workload-deployment-tooling
|
|
name: Workload release configuration and guards
|
|
summary: Helm/manifests, exact image pins, application runbooks and rollout/rollback.
|
|
owner: railiance-apps
|
|
status: draft
|
|
domain: financials
|
|
tags:
|
|
- railiance
|
|
- kubernetes
|
|
- helm
|
|
- deployment
|
|
- security
|
|
- netkingdom
|
|
- framework-reuse
|
|
maturity:
|
|
discovery:
|
|
current: D3
|
|
target: D4
|
|
confidence: medium
|
|
rationale: SCOPE.md places this repo precisely in the Railiance OAS Stack layering
|
|
(S5), scoped to application Helm releases, workload manifests, and operator
|
|
runbooks for user-facing services such as vergabe-teilnahme.
|
|
availability:
|
|
current: A2
|
|
target: A3
|
|
confidence: medium
|
|
rationale: 'Source interface assessed 2026-10-14: Helm/manifests, exact image
|
|
pins, application runbooks and rollout/rollback. Availability describes the
|
|
delivery form, not production acceptance. Release settings depend on underlying
|
|
platform and workload owners.'
|
|
external_evidence:
|
|
completeness:
|
|
level: C1
|
|
confidence: low
|
|
basis: scope_vs_intent_and_consumer_expectations
|
|
satisfied_expectations:
|
|
- Helm charts and Kubernetes manifests for application workloads
|
|
- smoke-test and dry-run check scripts, including a forgejo-smoke.sh already ahead
|
|
of the platform-wide Forgejo transition
|
|
broken_expectations: []
|
|
out_of_scope_expectations: []
|
|
reliability:
|
|
level: R1
|
|
confidence: low
|
|
basis: consumer_quality_signals
|
|
known_reliability_risks:
|
|
- no top-level packaging; tooling is a collection of shell scripts under tools/
|
|
discovery:
|
|
intent: Helm/manifests, exact image pins, application runbooks and rollout/rollback
|
|
includes:
|
|
- Helm/manifests, exact image pins, application runbooks and rollout/rollback
|
|
excludes:
|
|
- Release settings depend on underlying platform and workload owners
|
|
assumptions: []
|
|
use_cases:
|
|
- 'U12: Developer builds and publishes through controlled source, dependency and
|
|
runner paths'
|
|
- 'U13: Platform owner deploys and rolls back a workload with explicit substrate
|
|
and custody bindings'
|
|
research_memos: []
|
|
availability:
|
|
current_level: A2
|
|
target_level: A3
|
|
current_artifacts:
|
|
- SCOPE.md
|
|
target_artifacts: []
|
|
consumption_modes:
|
|
- CLI
|
|
- source
|
|
relations:
|
|
depends_on: []
|
|
supports: []
|
|
related_to:
|
|
- capability.security.iam-tooling-suite
|
|
evidence:
|
|
documentation:
|
|
- SCOPE.md
|
|
tests:
|
|
- tools/forgejo-smoke.sh
|
|
- tools/k8s-server-dry-run.sh
|
|
consumer_feedback: []
|
|
bug_reports: []
|
|
incidents: []
|
|
consumer_guidance:
|
|
recommended_for:
|
|
- Developer builds and publishes through controlled source, dependency and runner
|
|
paths
|
|
- Platform owner deploys and rolls back a workload with explicit substrate and custody
|
|
bindings
|
|
not_recommended_for:
|
|
- Release settings depend on underlying platform and workload owners
|
|
known_limitations:
|
|
- Release settings depend on underlying platform and workload owners
|
|
- 2026-10-14 architecture review estimates operational maturity separately; a registry
|
|
entry does not authorize execution or establish deployment.
|
|
promotion_history: []
|
|
---
|
|
|
|
# Workload release configuration and guards
|
|
|
|
Helm/manifests, exact image pins, application runbooks and rollout/rollback.
|
|
|
|
## Reuse boundary
|
|
|
|
Release settings depend on underlying platform and workload owners.
|
|
|
|
## Supported use cases
|
|
|
|
- U12: Developer builds and publishes through controlled source, dependency and runner paths
|
|
- U13: Platform owner deploys and rolls back a workload with explicit substrate and custody bindings
|
|
|
|
## Evidence and integration
|
|
|
|
- [SCOPE.md](../../SCOPE.md)
|
|
|
|
Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.
|