Files
claude-plugin-fleet-integra…/.claude-plugin/plugin.json
T
Oleks 8a28233417 preflight: make integration-preflight a mandatory step 0 with a dependency smoke test
Closes-part-of oleks/cluster#271.

- integration-preflight: framed as the non-skippable step 0 of any
  multi-step rollout; new procedure step 6 requires ONE real authenticated
  request against every external endpoint FROM THE RUNTIME CONTEXT, with
  the allowManagementFrom case (oleks/armer#171) as the worked example;
  output now carries a dependency table alongside the layer table;
  description rewritten so the skill actually routes on rollout-shaped work.
- onboard-host / integrate-service / finish-migration: each names
  integration-preflight as its step 0 entry gate.
- failure-catalog: adds F12 (external dependency never smoke-tested from
  the runtime context, oleks/armer#171) and F13 (preflight treated as a
  judgment call, oleks/cluster#260 + oleks/armer#171).
- README + plugin.json 1.0.0 -> 1.0.1.
2026-07-21 16:13:18 +03:00

25 lines
1.5 KiB
JSON

{
"name": "fleet-integration",
"version": "1.0.1",
"description": "Integration playbooks for the oleks fleet, distilled from the 2026-07-21 k3s-over-ZeroTier connectivity research (27 incidents, 9 recurring patterns — catalogued on the oleks/cluster wiki page K3s-over-ZeroTier-Connectivity). Core finding: the failures were integration-shaped, not platform-shaped — undeclared state, half-finished migrations, hardcoded environment assumptions, half-implemented lifecycles, watchdog amplification. Six skills cover the levels of the system: integration-preflight (declared-vs-live drift audit before building on top), onboard-host (join a host to the fleet network + k3s), integrate-service (service end-to-end: chart, Flux, ingress, DNS, secrets, DB, TLS, deploy tracking), ephemeral-lifecycle (scale-to-zero credential/member lifecycle rules), add-watchdog (health-check design that doesn't amplify failures), finish-migration (cutover discipline: done means old state REMOVED and declared==live). Playbooks encode failure classes, not current facts — they direct verification against live sources of truth (fleet-modules/cluster-topology.nix, the wiki) rather than restating values that rot.",
"author": {
"name": "oleks",
"email": "plugins@oleks.space"
},
"repository": "https://claude-plugins.oleks.space/plugins/fleet-integration.git",
"license": "MIT",
"keywords": [
"integration",
"playbook",
"fleet",
"onboarding",
"migration",
"lifecycle",
"watchdog",
"runbook",
"k3s",
"zerotier",
"self-hosted"
]
}