feat(orchestration): pool names, key/project guard, organisation-aware targets #2

Merged
crapougnax merged 5 commits from feat/orchestration-pool-name into develop 2026-11-07 07:37:32 +00:00
Member

Workloads may select nodes by the provider pool name (k8s.scaleway.com/pool-name). spec.cluster.pools.<key>.name now sets it (name_override of the kapsule-cluster module); without it the name stays <cluster>-<key>-pool. Validated (lowercase, digits, dashes). Tests updated (15 pass), typecheck OK.

🤖 Generated with Claude Code

Workloads may select nodes by the provider pool name (`k8s.scaleway.com/pool-name`). `spec.cluster.pools.<key>.name` now sets it (`name_override` of the kapsule-cluster module); without it the name stays `<cluster>-<key>-pool`. Validated (lowercase, digits, dashes). Tests updated (15 pass), typecheck OK. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Workloads may select nodes by the provider's pool name
(k8s.scaleway.com/pool-name); spec.cluster.pools.<key>.name sets it,
default unchanged (<cluster>-<key>-pool).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Before any plan, the description of the API key is read; a key whose
default project is not spec.projectId is refused. A scoped key that cannot
read its own description only warns: the per-target bucket policy of the
state is then the guard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot changed title from feat(orchestration): exact pool name per node pool to feat(orchestration): pool names, key/project guard, organisation-aware targets 2026-11-06 20:33:37 +00:00
The module works on the target id org/name handed over by the core:
kubeconfig in kube/<org>/<name>.yaml, ownership marker and journal keyed by
the id; the repository must declare the selected name (and organisation
when it declares one). target.yaml accepts metadata.organization; init
asks it and prefixes the state key with it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A pool with min 0 (GPU, on demand) was created with one node; it now starts
empty and the autoscaler adds nodes when needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each apply asks through the core's confirm(), which names the organisation
and target and refuses without a terminal unless TYCHO_ASSUME_YES=1. The
module's own --yes is removed: one way to confirm in CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
crapougnax merged commit 5f11a6674c into develop 2026-11-07 07:37:32 +00:00
crapougnax deleted branch feat/orchestration-pool-name 2026-11-07 07:37:32 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
tycho/modules!2
No description provided.