Where the reliability pattern came from.
Restricted self-managed platforms running high-consequence workloads. Every dependency reviewed, every image scanned, every certificate managed deliberately.
> Restricted self-managed OpenShift taught the patterns: declarative state, deterministic deploys, observability, graceful failure. AI delivery needs the same ones.
- 100+
- GPUs scheduled
- 58
- applications hosted
- weeks → hours
- provisioning cycles
// patterns that transfer
One config file defines truth. Everything renders from it; no manual editing, no drift.
Same inputs, same outputs, every time. The foundation of trust when you're deploying containers.
If you can't see what's happening, you can't fix it. Logs, metrics, traces on the path you operate.
Where AI meets infrastructure directly. Multi-generation GPU scheduling for ML teams running inference at scale.
// building trust in hostile environments
Air-gapped environments break assumptions. Every trust relationship has to be explicit.
Every dependency audited. Every container image is vendored, every chart pinned, every binary scanned. Trust nothing by default.
Explicit trust chains. Internal PKI everywhere. Internal certificate chains, managed trust stores. No implicit trust.
No easy escalation path. When something breaks, you learn from docs, source code, logs, and the system itself.
// the pattern
Config flows one direction. Sites customize, base charts deploy.
Environment-specific config: IPs, hostnames, feature flags. One file per site; overlays compose the final state.
Opinionated wrappers around upstream charts. Pinned versions, enterprise defaults, sync-wave ordering baked in.
// outcomes
Upgrades are boring. Change the version in config, let the pipeline render, watch dashboards. Platform upgrades shouldn't be events.
No tribal knowledge. Everything lives in Git. New engineers can trace exactly what happens from config change to deployed state. The pipeline is the documentation.
Developers stay unblocked. Self-service means the platform team isn't a bottleneck. Request infrastructure through Git, get infrastructure through Git.
// stack
// the bridge
The tooling page is how these patterns stay operable: /work/platform-tooling. 12-Factor AgentOps maps the same patterns to agent delivery.