User Guides on Kubemoot

The Starter Crew

Mon, 01 Jan 0001 00:00:00 +0000

kmctl create scaffolds a small, complete crew you can install on a fresh Kubemoot cluster and talk to within minutes. It is the Kubemoot equivalent of the nginx chart helm create produces: a working example you change into your own crew.

The starter crew is a read-only guide to the Kubernetes namespace it is installed into. Ask it what is running, what is wrong, and why. It reads the namespace with real tools and answers from what it found. It never changes anything.

Build a Crew

Mon, 01 Jan 0001 00:00:00 +0000

This guide builds a crew from its parts. A crew is a set of Kubernetes resources, so “building” one means declaring those resources - usually packaged together as a Helm chart so they version and deploy as a unit.

To see a complete small crew before writing your own, scaffold the starter crew with kmctl create.

What a crew is made of

Resource	Role in the crew
`Crew`	The team - groups agents by the `kubemoot.ai/crew` label, enables the discussion gateway, configures working memory.
`Agent`	Each participant: one coordinator, plus Toolers (and optionally Analysts). Declares capabilities, tools, RAG, and prompt refs.
`PromptModule`	Each agent’s behavior, written in ADL and composed by reference.
`Model` / `ModelProvider`	The models (by capability label) and the GPU-backed endpoints that serve them.
`MCPServer` / `MCPGateway`	The tools Toolers use, reached through the gateway.
`RAGSource`	Knowledge sources, indexed and made queryable.

Steps

1. Define the crew

Declare a Crew with the discussion gateway enabled, and a label every agent will share. See the Crew CRD reference for the full spec including the working-memory policy.

Compose a Crew

Mon, 01 Jan 0001 00:00:00 +0000

A crew is only as useful as its design. This guide covers the decisions that determine whether a crew’s coordinator routes questions intelligently and whether its Toolers and Analysts can answer them: which agents to include, how to write resumes the coordinator can reason over, how to ground the coordinator with broad knowledge and a well-crafted advisory brief, and how to give each Tooler the narrowly-scoped tools it needs and each Analyst the focused RAG knowledge it reasons over.

Write Agents & ADL

Mon, 01 Jan 0001 00:00:00 +0000

An agent’s behavior is its prompt, and in Kubemoot every prompt is written in ADL (the Architecture Definition Language) and stored in PromptModule CRs - never as inline prose in an Agent spec. This guide covers how to write ADL and how modules compose.

Why ADL

ADL expresses behavior as structured rules instead of free-flowing prose. The benefits are practical: a rule-based prompt is scannable (you can read what an agent will and won’t do at a glance), versionable (kubectl diff shows exactly what changed), and deployable without recompilation (a kubectl apply changes how an agent reasons). Prose prompts drift and hide their intent; ADL keeps it explicit.

Define Fitness Functions

Mon, 01 Jan 0001 00:00:00 +0000

A crew’s behavior is only as trustworthy as your ability to check it. Kubemoot implements architectural fitness functions as Kubernetes resources: you write a short scenario that asks the crew a real question and states what a good answer must satisfy, apply it, and the operator runs the crew live and scores each assertion pass or fail.

The shape of a scenario

A fitness scenario is ADL pseudo-code - a question plus assertions:

Onboard MCP Tools

Mon, 01 Jan 0001 00:00:00 +0000

A crew gains new abilities by gaining new tools, and tools come from MCP servers. You can declare them directly, or let Kubemoot’s autonomic onboarding acquire them when the crew hits a capability gap. This guide covers both.

Declare a tool server directly

When you already know the MCP server you want, declare an MCPServer and let an MCPGateway discover it. The operator handles the deployment, health probes, and - for stdio servers - the auto-injected mcp-bridge sidecar.

kmctl User Guide

Mon, 01 Jan 0001 00:00:00 +0000

kmctl is the command-line tool for Kubemoot. This guide covers installation, a runnable quickstart that walks through the core workflow, and shell-completion setup.

For the complete command reference, see kmctl Reference. For an overview of kmctl’s role in the ecosystem, see kmctl - the CLI.

Command structure

kmctl uses a hybrid noun-verb layout, chosen deliberately as the best fit for a domain CLI with deeply-nested resources and actions that have no clean kubectl equivalent.