The lab registers its own cluster as the infrastructure families (kubernetes, prometheus; capi with #56) the way an installation does — the Infrastructure preset resolves to x_kubernetes_*/x_prometheus_* with management_cluster=agentlab, and the fake fleet retires

[teemow]

Problem

On an installation the infrastructure servers are family members rendered by agent-platform-mcps: <cluster>-mcp-kubernetes, <cluster>-mcp-capi, <cluster>-mcp-prometheus, each with spec.family (x_kubernetes_<tool> with a management_cluster argument) and the agent-platform.giantswarm.io/tool-group: infrastructure label; there is no family-less singleton. The lab differs in three ways:

• the connectivity chart's bundled mcp-kubernetes MCPServer is a family-less singleton (x_mcp-kubernetes_*), labelled infrastructure;
• the lab's mcp-prometheus is registered through agent-platform-mcps as a singleton on purpose (group observability, kept outside muster.families so it mirrors the singleton's UX) — and therefore carries no tool-group label;
• six fake-fleet fixtures stand in for the families (The fake fleet is opt-in: a default lab registers only its own MCP servers — no <family>-lab-01/02 rows asking for sign-in in the portal's Tool explorer and MCP servers page #167 makes them opt-in).

Result in the agent create flow's Tools step (2026-09-12): the Infrastructure preset resolves to the six x_mcp-kubernetes_* tools only — no Prometheus, although the preset's own description names mcp-kubernetes, mcp-capi and mcp-prometheus — while the catalogue shows three families "awaiting sign-in" that no one can sign in to. Confusing for anyone testing the lab, and a shape no installation has.

Decision (2026-09-12): families only, on installations and in the lab alike. The lab is heading for several clusters anyway (#56, #57 add CAPI and cluster-manager), so a single-cluster special case buys nothing.

Proposed solution

• The lab's own servers are registered as members of the families, with the lab's cluster as the instance: agent-platform-mcps.mcpServers entries for mcp-kubernetes and mcp-prometheus with cluster: agentlab and groups kubernetes / prometheus (family block and tool-group label come from the chart's defaults; capi joins when platform.clusters: install kaas-standalone (as a Flux HelmRelease) next to the Agent Platform chart in the lab; headless clusters-test — CAPI and CAPA/CAPZ controllers ready, Release CRs synced, the giantswarm Organization present, no cloud credential #56 lands, with muster.families.capi as the fleet configures it).
• The connectivity chart's singleton registration is not rendered in the lab — this needs a knob in giantswarm/agent-platform (feat(connectivity): the bundled mcp-kubernetes registers as a family member (cluster + family) or not at all — a single-installation deployment gets the same x_kubernetes_* family UX as the fleet agent-platform#403); until it exists the lab cannot avoid two registrations of the same server.
• Proofs and docs move to the family UX: x_kubernetes_<tool> / x_prometheus_<tool> with management_cluster: agentlab; platform-test's mcp-kubernetes and mcp-prometheus steps call the family tools; the toolset proofs assert that preset:infrastructure resolves to both families; the "per-server prefix, no management_cluster argument" notes in the skill-facing docs go.
• The fake-fleet fixture is deleted (its opt-in, The fake fleet is opt-in: a default lab registers only its own MCP servers — no <family>-lab-01/02 rows asking for sign-in in the portal's Tool explorer and MCP servers page #167, is the interim step), together with the servergroups.go arithmetic that depended on it: Infrastructure = the lab's two (later three) family members.

Timing: after the kagent API v2 migration is done (the migration has priority).

Acceptance criteria

• kubectl get mcpservers -n agent-platform on a default lab lists agentlab-mcp-kubernetes and agentlab-mcp-prometheus (family members, tool-group: infrastructure, management-cluster: agentlab) and no family-less mcp-kubernetes singleton
• The Tools step's Infrastructure preset resolves to the kubernetes and prometheus family tools; the catalogue lists no server that cannot be signed in to
• platform-test, toolsets-test, backstage-test, agents-test green on the family UX; the docs (platform.md, backstage.md, the lab's MCP usage notes) describe it
• The fake-fleet fixture and its code are gone