skills.rest
RHEcosystemAppEng
RHEcosystemAppEngOFFICIAL
Explore all skills by this author →
GitHub

debug-rbac

Diagnose OpenShift RBAC permission failures from pod logs and Role bindings.

48|31|Updated Feb 2, 2026
Search Tags:#RBAC#Kubernetes#OpenShift#diagnosis#permission failure
One-click install
npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-rbac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-rbac
Source: https://github.com/RHEcosystemAppEng/agentic-plugins/tree/main/rh-developer/skills/debug-rbac
Command: npx skills add https://github.com/RHEcosystemAppEng/agentic-plugins --skill debug-rbac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires resources_get, resources_list, pods_list, pods_log, events_list, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the diagnosis of OpenShift RBAC permission failures, helping to identify and resolve issues that lead to 403 Forbidden errors when accessing the Kubernetes API.

Core Features & Use Cases

  • Automated RBAC Diagnosis: Identifies and analyzes permission failures using pod logs, readiness probes, ServiceAccount bindings, and Role/RoleBinding configurations.
  • Multi-Step Analysis: Automates a multi-step diagnosis process including error analysis, service account identification, role analysis, and remediation history for regression detection.
  • Use Case: When you encounter 403 Forbidden errors on OpenShift, use this Skill to automatically diagnose the issue and suggest remediation steps.

Quick Start

Run the /debug-rbac Skill to diagnose RBAC permission failures for a specific OpenShift deployment.

Frequently Asked Questions about debug-rbac

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose OpenShift RBAC permission failures causing 403 Forbidden errors?▼

Diagnosing OpenShift RBAC permission failures involves analyzing pod logs, readiness probes, ServiceAccount bindings, and Role/RoleBinding configurations to identify why the Kubernetes API returns a 403 Forbidden error.

What is the best way to troubleshoot Kubernetes API 403 Forbidden errors on OpenShift?▼

The best way to troubleshoot Kubernetes API 403 Forbidden errors is automating a multi-step diagnosis that checks service account identification, role analysis, and remediation history to pinpoint the missing permission.

Do I need specific tools to access OpenShift resources for RBAC diagnosis?▼

Yes, diagnosing RBAC issues requires specific tools including resources_get, resources_list, pods_list, pods_log, and events_list to access and analyze the necessary OpenShift cluster resources.

How does ServiceAccount binding analysis work when diagnosing OpenShift permission failures?▼

ServiceAccount binding analysis works by examining the pod's ServiceAccount and cross-referencing its Role and RoleBinding configurations to detect the missing permissions causing the OpenShift RBAC failure.

Can I track remediation history for OpenShift RBAC permission failures?▼

Yes, you can track remediation history for OpenShift RBAC permission failures. The diagnosis process includes checking remediation history specifically for regression detection to ensure past fixes remain effective.

Related Skills

Explore More Software Engineering Skills→
RHEcosystemAppEngRHEcosystemAppEng
48

debug-scc

Diagnose OpenShift SCC violations by analyzing Deployment, ReplicaSet, Event, and ServiceAccount data.

Official
Advanced
RHEcosystemAppEngRHEcosystemAppEng
48

debug-pod

Diagnose OpenShift pod failures by collecting status, events, logs, and resource information.

Official
Intermediate
hung-phanhung-phan

health-checks

Optimize Kubernetes liveness, readiness, and startup probe configurations.

Community
Advanced
kcns008kcns008
3

kubernetes-operations

Automate Kubernetes and OpenShift cluster upgrades, backups, node management, and monitoring.

Community
Advanced