Uploaded November 2026 | Updated November 2026, 13 hours ago
Tired of manually diagnosing cluster alerts? With Red Hat OpenShift 5, agentic troubleshooting acts as your site reliability engineering (SRE) autopilot to automatically respond to alerts.
Manually troubleshooting cluster alerts consumes valuable time and resources. Autonomous agentic troubleshooting with OpenShift Lightspeed continuously monitors your environment and diagnoses issues in the background, freeing up your team for higher-priority work.
Red Hat’s Ju Lim demonstrates how to reduce incident response times by using an AI agent that proposes 1-click fixes, all while maintaining complete human-in-the-loop governance over execution.
Watch how Agentic Lightspeed correlates cluster telemetry logs and Kubernetes resource metadata to find root causes, and how approved remediations execute safely in an isolated pod using least-privileged role-based access control (RBAC), ensuring zero unauthorized lateral movement.
Timestamps:
00:00 Introduction
00:45 Enable the alert manager adapter
01:02 Review firing critical alerts
01:23 Analyze the agentic run and troubleshooting phases
02:11 Configure human-in-the-loop governance policies
02:35 Review root cause analysis and proposed remediation
03:04 Execute and verify the remediation
03:53 Manage agentic workflows via the command-line interface (CLI)
Explore:
💡 Discover OpenShift 5→ redhat.com/en/technologies/cloud-computing/openshift-5sc_cid=RHCTG0260000501072
✨ Read the release notes → docs.redhat.com/en/documentation/openshift_container_platform/5.0sc_cid=RHCTG0260000501072
#RedHat #OpenShift #Lightspeed #AgenticAI #Kubernetes #Troubleshooting
Tired of manually diagnosing cluster alerts? With Red Hat OpenShift 5, agentic troubleshooting acts as your site reliability engineering (SRE) autopilot to automatically respond to alerts.
Manually troubleshooting cluster alerts consumes valuable time and resources. Autonomous agentic troubleshooting with OpenShift Lightspeed continuously monitors your environment and diagnoses issues in the background, freeing up your team for higher-priority work.
Red Hat’s Ju Lim demonstrates how to reduce incident response times by using an AI agent that proposes 1-click fixes, all while maintaining complete human-in-the-loop governance over execution.
Watch how Agentic Lightspeed correlates cluster telemetry logs and Kubernetes resource metadata to find root causes, and how approved remediations execute safely in an isolated pod using least-privileged role-based access control (RBAC), ensuring zero unauthorized lateral movement.
Timestamps:
00:00 Introduction
00:45 Enable the alert manager adapter
01:02 Review firing critical alerts
01:23 Analyze the agentic run and troubleshooting phases
02:11 Configure human-in-the-loop governance policies
02:35 Review root cause analysis and proposed remediation
03:04 Execute and verify the remediation
03:53 Manage agentic workflows via the command-line interface (CLI)
Explore:
💡 Discover OpenShift 5→ redhat.com/en/technologies/cloud-computing/openshift-5sc_cid=RHCTG0260000501072
✨ Read the release notes → docs.redhat.com/en/documentation/openshift_container_platform/5.0sc_cid=RHCTG0260000501072
#RedHat #OpenShift #Lightspeed #AgenticAI #Kubernetes #Troubleshooting










