The umbrella orchestrator blueprint of Krateo PlatformOps: one helm install that
self-bootstraps the composition engine and sequences every component blueprint into an
ordered, readiness-gated platform rollout.
A chart that bundles no components — it sequences them: Pass A registers a
CompositionDefinition per component, Pass B emits each component Composition only
once its dependencies are Ready=True and its generated CRD is served. The chart also
registers itself as an Installer composition, so the whole platform converges —
and heals, and upgrades, and tears down in order — on the engine's reconcile loop.
Full picture: docs/index.md.
helm install installer \
oci://ghcr.io/krateo-platformops/charts/installer \
--version 0.3.11 \
--namespace krateo-system --create-namespace \
--set bootstrap.coreProvider.enabled=truebootstrap.coreProvider.enabled=true is required on a bare cluster (Kubernetes
≥ 1.36); there is no step 2. Upgrades, uninstall and the agent-only profile:
docs/usage.md.
See docs/configuration.md. Most used:
| Setting | Default | Effect |
|---|---|---|
features.* |
portal on, agents off | Feature gates over the component DAG (portal, oasgenProvider, coreAgents, specialistAgents). |
exposure.type / exposure.port |
LoadBalancer / unset |
How browser-facing components are exposed; NodePort for kind/bare-metal; port = one shared port. |
componentValues.<name> |
curated defaults | Per-component Composition-spec overrides, deep-merged — the only durable customization channel. |
In examples/, each with preconditions and the one command
(docs/examples.md):
- bootstrap-install — the canonical bare-cluster install, NodePort exposure.
- component-overrides —
componentValuesoverrides at install time or on the live Installer CR.
- docs/index.md — the map of the bundle.
- docs/overview.md — bootstrap vs composition mode, Pass A/B, the self-reconcile loop, the teardown hooks.
- docs/usage.md — install / upgrade / day-2 / uninstall.
- docs/configuration.md — the whole values surface.
- docs/api.md — the generated Installer CRD + emitted objects;
component-pins.yamlas version source of truth. - docs/examples.md — the runnable examples.
- docs/release.md — how a release ships; the GVK migration.
- docs/log.md — curated history.
- docs/llms.txt — the version-pinned agent index.
Validate locally with helm dependency build chart/ && helm lint chart/ (CI runs the
same plus a render smoke test and this doc bundle's conformance check). Releases ship
from a plain-semver tag (no v prefix) via the canonical release-oci workflow:
docs/release.md.