CrewForge on Kubemoot

Install and connect

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

CrewForge installs from a .vsix file and connects through the kubeconfig you already use. This page covers the prerequisites, the install, how CrewForge chooses a cluster, and what it tells you when it cannot reach one.

Prerequisites

You need	For
VS Code 1.95 or later	Running the extension.
A kubeconfig with access to a cluster that runs the Kubemoot operator	Everything. CrewForge lists the crews your account can read.
`kubectl` on your PATH	Deploying a bundle of plain manifests (`kubectl apply --server-side`).
`helm` on your PATH	Deploying a crew chart, and Lint. Without it, Lint says where to get it.
`kmctl` on your PATH, a current release (its `kmctl create` takes `--display-name`)	New Kubemoot Crew Here and Create Crew, which run `kmctl create --chart` to scaffold the starter crew. CrewForge checks kmctl before it asks you anything and names the minimum it needs.
`git` on your PATH (optional)	Recording the revision a crew was deployed from, and deploying an earlier commit.

Browsing crews and chatting need only the kubeconfig. Developing a crew needs the rest. Your account’s cluster permissions are listed in Settings and permissions.

Develop a crew in VS Code

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

This guide walks the whole loop on one small example: a helpdesk crew scaffolded from the starter crew, a read-only guide to its own Kubernetes namespace. You create it, change it, deploy it to a namespace, ask it something, and redeploy after an edit. Everything happens in the editor, without GitOps: CrewForge deploys with Helm straight to a namespace, and never commits or pushes. Flux rollouts stay the outer loop.

Views and dashboards

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

This page is the reference. For a guided tour, see Develop a crew in VS Code.

What CrewForge changes

CrewForge applies only Kubemoot custom resources and Helm releases of them. It never deletes a namespace or any other kind of object; the operator owns cleanup through finalizers and owner references. Add … and Remove from Source… change only files of a source. Anything that deletes files, such as Delete Source…, moves them to your trash. Actions that only read are marked “nothing” in the action reference below.

Fitness from the editor

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

Fitness functions measure whether a crew does its job. CrewForge runs them, shows their results, and lets you hold or end a run, all against the same Kubemoot resources kubectl and kmctl use. Writing the scenarios themselves is covered in Define Fitness Functions.

Your scenarios

A crew source keeps its fitness definitions in a fitness/ folder, inside a chart or beside a bundle. Expand Fitness Scenarios under a source to list them: the scripts of each CrewFitnessSuite, each CrewFitness, and loose .adl (ADL) and .md (prose) scripts.

Settings and permissions

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

Settings

Open Settings in VS Code and search for crewforge.

Setting	Default	Meaning
`crewforge.kubeconfig`	empty	Path to a kubeconfig file. Empty uses `KUBECONFIG`, then `~/.kube/config`.
`crewforge.context`	empty	Kubernetes context to use. Empty uses the kubeconfig’s current context.
`crewforge.namespaces`	`[]`	Show crews only in these namespaces. Set it when your account may read only some namespaces. Empty shows every namespace you can read.
`crewforge.streamTimeoutSeconds`	`600`	Longest a single turn may stream before CrewForge gives up on it. The minimum is 60.
`crewforge.dashboardService`	empty	The Kubemoot dashboard’s Service as `namespace/name:port`. CrewForge reads it through the Kubernetes service proxy, read-only, for thread counts, discussion failures, fitness scores, and archived iterations. Empty finds the Service labelled `app.kubernetes.io/part-of=kubemoot` whose `app.kubernetes.io/name` is `dashboard` (the operator chart’s subchart) or `kubemoot-dashboard` (a standalone install). Add an optional base path, `namespace/name:port/base`, when the dashboard serves under a path such as `/dashboard`.
`crewforge.dashboardUrl`	empty	The address of the Kubemoot dashboard for this cluster. Powered by Kubemoot in a chat opens it, and Open this turn in the Kubemoot dashboard appears under an answer only when this is set. Behind a `kubectl port-forward`, use the local address. Empty makes Powered by Kubemoot open this setting.

The Kubemoot dashboard is optional. Without it, the parts of the crew and fitness dashboards that come from it (discussion counts, agent failures, judge scores, and the results workbook download) say they are not available.

Troubleshooting

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

Where the logs are

CrewForge writes to its own output channel. Open View > Output and choose CrewForge from the drop-down. It holds page errors, Lint failures, and the output of the helm and kubectl commands behind a deploy, redeploy, or undeploy. A failed deploy opens it for you. A failed kmctl create shows kmctl’s own message in a dialog.

For a bug report, run CrewForge: Show Connection Info and use its Copy button. It gives CrewForge’s version, the Kubemoot operator’s version, the Kubernetes server version, and the context and server address.