Changed
- BREAKING (Kubernetes mode):
type: stdioMCPServers are rejected. A stdio server is started as a subprocess of the muster process, so in a deployed aggregator “may write MCPServer resources” implied “may execute code in the muster pod as muster’s ServiceAccount” (which holdsgeton Secrets in its namespace and cluster-wide write on the muster CRDs). Kubernetes mode now refuses stdio at every layer:mcpserver_validate/mcpserver_create/mcpserver_updatefail the tool call with a message namingstreamable-http/sseas the alternative; a stdio MCPServer applied straight through the API server reconciles tostatus.state: Failedwith the same message instatus.lastErrorand is never started (an already-running one from an older muster is torn down); and the orchestrator and service layers refuse to build a stdio client at all, so no path reachesNewStdioMCPClient. Deployments with stdio MCPServers must run those servers as their own workload and re-register them withtype: streamable-httportype: sse. Filesystem mode —muster serveagainst a local config directory, i.e. the CLI, where launching subprocesses is the point — is unchanged. (#1067)