OpenShift Lightspeed gains a natural-language path into multicluster fleet health
A Technology Preview MCP server turns OpenShift Lightspeed prompts into Red Hat Advanced Cluster Management search queries across managed clusters.
Red Hat has published a deployable pattern for connecting OpenShift Lightspeed to Red Hat Advanced Cluster Management (ACM), giving platform teams a natural-language interface to fleet-wide search data. The bridge is a new ACM search Model Context Protocol (MCP) server, currently labeled Technology Preview.
What changed
The MCP server runs on the ACM hub cluster and translates prompts into structured queries against the ACM Search API. Red Hat’s walkthrough installs it from a Helm chart, which creates the deployment, service, service account and RBAC resources needed to reach that API.
OpenShift Lightspeed then registers the endpoint through its OLSConfig custom resource. The example enables the MCPServer feature gate, points Lightspeed at the in-cluster service URL and uses Kubernetes service-account authentication. The request path is straightforward: Lightspeed receives a question, calls the MCP endpoint, the server queries ACM Search, and structured results return to the language model for analysis.
That matters because the integration is not just another chat front end. ACM already holds a fleet-level view; MCP makes that view available as a bounded tool rather than asking a model to infer cluster state from prose.
What operators can ask
Red Hat demonstrates three query patterns. One checks which managed clusters run an OpenShift release older than 4.21. Another retrieves pods in a named namespace on a specific production cluster. A third asks for unhealthy virtual machines across the entire fleet and returns a VM stuck in an ErrorUnschedulable condition with diagnostic guidance.
The first example also shows tool composition. Lightspeed uses the new ACM search MCP server to enumerate clusters, while its built-in resources_get tool reads version details from ManagedCluster and ManagedClusterInfo resources on the hub.
The approval trade-off
The walkthrough characterizes the ACM search server as read-only: it queries, filters and retrieves data without changing cluster state. Red Hat therefore shows an optional configuration that disables human approval for these tool calls, avoiding a confirmation step on every search.
That is a consequential configuration choice, even for a read-only endpoint. Platform teams should validate the service account’s RBAC scope and the data exposed to the model before removing approvals. The article’s design at least keeps the tool boundary explicit and uses Kubernetes authentication rather than embedding a static credential.
What to try
This is a lab pattern, not a general-availability product promise. The MCP server is a Technology Preview, and Red Hat directs users to its upstream repository for testing. Teams evaluating it should begin with a constrained hub, confirm that results respect their intended access boundaries, and compare the generated answers with ACM Search output before putting the workflow near incident response.
For OpenShift platform teams, the useful shift is architectural: Lightspeed can now call a purpose-built fleet search tool, and ACM remains the system retrieving the underlying multicluster state.
sources
comments · 0