oc-fleet-ops
Multi-container / orchestration deployment operator for self-managed infrastructure. Declares topology (containers/services × target environment), provisions infra with the right IaC tool (Terraform/OpenTofu when it fits, else Ansible/cloud-init/k8s-manifests/ Helm/Nomad/Compose), rolls the fleet with a rollout strategy, verifies fleet-wide health, and operates day-2 (scale/drain/replace/rollback). Specifically lands the modules oc-modularize-ops carves out of a monolith. Use for /oc-fleet, "deploy multiple containers", "kubernetes", "terraform", "orchestrate containers", "on-prem deployment", "deploy to VMs", "self-managed infra", "container fleet". Complements oc-deploy-ops (single-app managed PaaS): managed app → deploy-ops; multi-container/self-managed/IaC → fleet-ops. Trigger on multi-container / IaC / self-managed deployment.
Original · translation did not pass checksTarget: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Fleet Ops
- /oc-fleet — Command Reference
- How This Skill Fits the Build Pipeline
- Operating model — gated ops phases
- Phase 0 — Topology (/oc-fleet topology)
- Phase 1 — Provision (/oc-fleet provision) — IaC, Terraform when it fits
- Phase 2 — Deploy (/oc-fleet deploy)
- Phase 3 — Verify (/oc-fleet verify)
On first invocation, read references/orchestrator.md and follow its welcome protocol. Deploy and operate one-or-more containers across arbitrary, self-managed environments — the territory oc-deploy-ops routes elsewhere today. Where deploy-ops is opinionated about a single app on a managed PaaS (Workers, Render, Fly, Shuttle), Fleet Ops owns the messier other half: multi-container orchestration (k8s/Nomad/Compose/Swarm), infrastructure-as-code (Terraform and its alternatives), and arbitrary environments (on-prem Linux VMs, GCE, bare metal). It is also the skill that lands the modules oc-modularize-ops carves out of a former monolith — once the seams are proven, the fleet is where those modules actually run. This is not a tri-agent forge and not a managed-PaaS deployer. It is a gated ops operator: declare what runs where, provision the infra with the IaC tool that fits (not Terraform by reflex), roll the fleet behind a strategy, verify health across every replica and cross-service edge, then operate day-2 — scale, drain, replace, roll back. The IaC apply step is the highest-blast-radius operation in the entire opchain catalog, so it is gated behind a mandatory dry-run/plan that never
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-fleet-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:26.922Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.