# OpenShift 5 adds agentic AI troubleshooting with mandatory human approval guardrails

> **Key takeaway:** Red Hat OpenShift 5 introduces an opt-in agentic troubleshooting preview that automates diagnostic runs but requires explicit human approval for any cluster state changes, with full audit tracing via Tempo.

**Published:** 2026-11-12T06:02:48.185564+00:00 
**Source:** Red Hat Blog 
**Category:** distro-news 
**Canonical URL:** https://fosswire.org/news/openshift-5-adds-agentic-ai-troubleshooting-with-mandatory-h.html 

## Summary
Red Hat has released OpenShift 5 with new AI-augmented observability capabilities centered around OpenShift Lightspeed, which synthesizes Prometheus metrics, pod logs, and OpenTelemetry traces into structured incident diagnoses. The platform now offers conversational troubleshooting through a Model Context Protocol (MCP) server connection, natural-language dashboard generation for the Perses metrics visualization tool, and an opt-in agentic workflow that executes oc and kubectl commands automatically when alerts fire.

The agentic troubleshooting feature, available as a technology preview, stages proposed remediation plans into a decision queue for human review rather than applying changes autonomously. OpenShift Lightspeed requires administrators to bring their own LLM via the operator, with version 2 needed for agentic features and version 1.1.5 or later supporting the conversational troubleshooting mode on OpenShift 4.22 and later. All AI-assisted dashboard panels carry an AI-assisted badge with inspectable underlying PromQL queries.

## OpenShift 5 observability architecture and safety model
- **OpenShift Lightspeed operator versioning:** Conversational troubleshooting requires operator 1.1.5+ on OpenShift 4.22+, while agentic troubleshooting requires OpenShift 5 with Lightspeed operator 2 and a configured tool-calling LLM, with no default model shipped.
- **Telemetry synthesis via MCP:** Lightspeed connects to an observability Model Context Protocol server to inspect Prometheus metrics, pod logs, and OpenTelemetry traces, assembling findings into Source-Signal-Finding structured output for human review.
- **AI-assisted Perses dashboards:** Natural-language queries generate PatternFly-themed panels in the OpenShift console through the cluster observability operator 1.6, with visible AI-assisted badges and inspectable PromQL for verification before pinning to production dashboards.
- **Agentic workflow safety design:** The agent watches Alertmanager with existing receiver adapters, halts execution and escalates to humans if remediation fails to clear the alert condition, and never loops or guesses alternative fixes.
- **Three-layer guardrail architecture:** Mandatory human approval for all cluster state changes, RBAC-sandboxed ephemeral execution environments for remediation tasks, and complete audit tracing recorded in Tempo with Agentic Runs UI integration in the OpenShift console.

## Why it matters
For platform engineering teams running Kubernetes at scale, OpenShift 5's structured approach to AI-assisted incident response offers a reference architecture for safe autonomous operations that competing distributions may emulate. The requirement to bring your own LLM and the explicit safety-first design with non-negotiable human approval gates addresses enterprise compliance concerns that have slowed AI adoption in production infrastructure tooling, while the open-source Perses integration provides a migration path for teams seeking Grafana alternatives.