openshift-expert
Audited by Runlayer on Feb 24, 2026
Malicious tool definition detected
Tool: README.md Description: # OpenShift Expert Skill An intelligent AI skill that provides deep OpenShift platform expertise for test failure analysis, cluster troubleshooting, and root cause determination.
Malicious tool definition detected
Tool: SKILL.md [1/4] Description: --- name: openshift-expert description: OpenShift platform and Kubernetes expert with deep knowledge of cluster architecture, operators, networking, storage, troubleshooting, and CI/CD pipelines.
Tool: SKILL.md [2/4] Description: ServiceAccount, token validity - **OAuth Failures** - Pattern: `oauth authentication failed`, `invalid_grant`, `unauthorized_client` - Root causes: OAuth server down, identity provider config, certificate issues - First check: OAuth operator, identity provider CR, oauth-openshift pods ### 2.
Tool: SKILL.md [3/4] Description: ├─ Not running → Why?
Tool: SKILL.md [4/4] Description: 1, 2, 3] - Category: [Product Bug/Test Automation/Infrastructure/Configuration] **Affected Components**: - [Component A]: [role and state] - [Component B]: [role and state] **Dependency Chain**: [how components interact] ## Troubleshooting Evidence [Commands run and their results - specify omc or oc] ## Recommended Actions 1.
Malicious tool definition detected
Tool: knowledge/failure-patterns.md [1/3] Description: # OpenShift Failure Patterns Catalog Comprehensive catalog of common failure signatures with root causes, troubleshooting steps, and resolutions.
Tool: knowledge/failure-patterns.md [2/3] Description: | PVC pending | Check storage provisioner | Ensure StorageClass exists | | Pod limit reached | Increase max pods per node | Consolidate workloads | --- ## Operator Failures ### ClusterOperator Degraded **Signature Patterns**: ``` clusteroperator/authentication is degraded because OAuthServerDeploymentDegraded clusteroperator/ingress is degraded because IngressControllerDegraded clusteroperator/monitoring is degraded because UpdatingPrometheu
Tool: knowledge/failure-patterns.md [3/3] Description: "pods" forbidden: User "X" cannot get resource "Y" in API group "Z" Unauthorized ``` **Root Causes**: 1.
Malicious tool definition detected
Tool: knowledge/operators.md [1/4] Description: # OpenShift Cluster Operators Reference Detailed troubleshooting guide for core OpenShift cluster operators.
Tool: knowledge/operators.md [2/4] Description: | grep daemon omc/oc logs -n openshift-machine-config-operator machine-config-daemon-<node> # Check node status omc/oc get nodes omc/oc describe node <node-name> | grep -A 10 "Conditions:" # Check for stuck drains (live only) oc adm drain <node> --dry-run # See what's blocking # Check CSRs (certificate signing requests) omc/oc get csr omc/oc get csr | grep Pending # Should be approved automatically ``` **MachineConfigPool States**: - `UPDATED=True`
Tool: knowledge/operators.md [3/4] Description: Check router pods omc/oc get pods -n openshift-ingress # Check router logs omc/oc logs -n openshift-ingress router-default-<id> # Check specific route omc/oc get route -n <namespace> omc/oc describe route <route-name> -n <namespace> ``` **Dependencies**: dns, network --- ### authentication **Purpose**: OAuth server for user authentication **Critical**: High - users cannot log in without authentication **Common Issues**: 1.
Tool: knowledge/operators.md [4/4] Description: -A # Check InstallPlans omc/oc get installplan -A # Check ClusterServiceVersion (CSV) omc/oc get csv -A ``` **Dependencies**: kube-apiserver, image-registry (for operator images) --- ## Quick Reference: Degraded Operator Workflow ``` Operator Degraded ├─ 1.
Malicious tool definition detected
Tool: scripts/categorize-failure.py Description: #!/usr/bin/env python3 """ Categorize OpenShift test failures using pattern matching.