feat(orchestration): targets from target.yaml, guided run, several clusters #1
No reviewers
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tycho/modules!1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/orchestration-engine"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Replaces the shell placeholder of
@tycho/orchestrationwith the engine of RFC-001 §3: a Kubernetes target described bytarget.yaml, built and kept up to date by a guided, resumable run. Onetychomanages several targets.What it does
target.yaml: types and fail-fast validation. Every problem is listed at once; no default for instance values (publicIps,egressGateway, Kubernetes version…); placeholders (example.com,TODO) and branch refs are refused.context add|use|list|remove,--target,TYCHO_TARGET. Never guesses. One kubeconfig per target (0600,~/.config/tycho/orchestration/kube/), always passed explicitly to kubectl.infrarecipe (Terraform modules).public-ips(durable,prevent_destroyin the module) andcluster(network, egress gateway on the reserved IP, Kapsule, free list of pools incl. GPU/taints/scale-to-zero, extra modules fromspec.infra.modules).apply): public IPs → DNS (stops with exit 3 and the list of records until public resolvers return them) → reverse DNS → cluster → kubeconfig + ownership marker → stacks inrequiresorder. State in.tycho/journal.jsonof the target repository.kubectl kustomize, then${VARIABLE}substitution limited to declared and built-in names (other${...}untouched); secrets only from SOPS (secrets.enc.yaml).Guards
--yesfor CI).kube-system/tycho-targetmust match the target name and cluster id.Checks
bun test: 14 tests (validation, roots, plan summary, DNS records, stack order and values, substitution, contexts).tsc --noEmitOK.terraform validateagainst the real catalogue modules fetched fromqtrn-io/clusterat a pinned commit.index.js(run(args, ctx)): contexts, validate, status, plan stops cleanly without credentials.Not yet
Ephemeral IPs, providers other than Scaleway, Podman,
tycho render(Argo CD CMP), cost in the plan. Version left at 0.1.0: the release number is decided at release time.🤖 Generated with Claude Code
Replaces the shell placeholder with the engine of RFC-001 §3: - target.yaml: types and fail-fast validation (every problem listed, no default for instance values, placeholders and branch refs refused); - contexts: one tycho manages several targets (context add/use/list, --target, TYCHO_TARGET); one kubeconfig per target, 0600, outside the repo; - catalogues fetched at a pinned ref; Terraform roots generated from the catalogue modules: durable public IPs and cluster, each in its own state; - guided run: public IPs, stop until DNS records exist, reverse DNS, cluster, kubeconfig and ownership marker, stacks in requires order; - guards: saved plans only, any destroy or replace refused, confirmation before each apply, cluster ownership checked before every kubectl change; - stacks: ${VARIABLE} substitution limited to declared and built-in names, secrets only from SOPS. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Pushed
refactor(orchestration): targets come from the core: contexts moved to the core (tycho/tycho PR feat/contexts). The module now acts onctx.targethanded over by the core and refuses non-kubernetes targets. Tested end to end with the compiled core:tycho module link,tycho context add/use,--target,TYCHO_TARGET.