skills.rest
openshift
openshiftOFFICIAL
Explore all skills by this author →
WebsiteGitHub

node-not-ready

Diagnose NotReady or SchedulingDisabled OpenShift nodes and prescribe recovery actions.

71|88|Updated Nov 8, 2023
Search Tags:#kubernetes#triage#openshift#notready#scheduling-disabled#node-diagnosis#cluster-recovery
One-click install
npx skills add https://github.com/openshift/lightspeed-service --skill node-not-ready
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-not-ready
Source: https://github.com/openshift/lightspeed-service/tree/main/skills/node-not-ready
Command: npx skills add https://github.com/openshift/lightspeed-service --skill node-not-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Troubleshoot NotReady or SchedulingDisabled node status in an OpenShift cluster, guiding users to identify root causes and restore node health.

Core Features & Use Cases

  • Identify affected nodes and determine whether the node is a control plane or worker.
  • Read and interpret common node conditions (MemoryPressure=True, DiskPressure=True, PIDPressure=True, NetworkUnavailable=True, Ready=False) to pinpoint failures.
  • Provide actionable recovery steps, including checking Machine/MachineSet status, remediation actions, CSR approvals, and network plugin health.

Quick Start

Diagnose a NotReady node and outline the immediate triage steps to restore it.

Frequently Asked Questions about node-not-ready

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

FAQPage Schema
How do I diagnose a NotReady node in OpenShift?▼

Diagnose a NotReady OpenShift node by executing a stepwise triage protocol that checks node conditions, machine state, network plugin health, and certificates to pinpoint root causes.

Why is my OpenShift node SchedulingDisabled and how do I fix it?▼

An OpenShift node is SchedulingDisabled during maintenance or drainage. Restore scheduling by checking Machine and MachineSet status, approving pending CSRs, and verifying network plugin health.

What do MemoryPressure and DiskPressure conditions mean in Kubernetes node triage?▼

MemoryPressure and DiskPressure are Kubernetes node conditions indicating resource exhaustion. Interpreting these during triage helps pinpoint failures and prescribe targeted recovery actions for cluster health.

Can I recover a failed control plane node using the same steps as a worker node?▼

The triage protocol applies to both control plane and worker nodes. It identifies the node type first, then prescribes appropriate recovery actions based on specific conditions and machine state.

How do I troubleshoot NetworkUnavailable status during OpenShift node recovery?▼

Troubleshoot NetworkUnavailable status by inspecting network plugin health as part of the node diagnosis protocol. This identifies connectivity failures and prescribes recovery actions to restore node readiness.

What is the best way to restore cluster health after a node failure in OpenShift?▼

The best way to restore cluster health after a node failure is to apply a post-failure recovery protocol that checks machine state, approves CSRs, and resolves network or certificate issues affecting nodes.

Related Skills

Explore More Software Engineering Skills→
tomazbtomazb
2

openshift-cluster-health-check

Assess OpenShift cluster health with a 17-phase diagnostic workflow.

Community
Advanced
bnaylorbnaylor
4

microk8s-janitor

Automate rolling upgrades for HA MicroK8s clusters via SSH with stateful recovery.

Community
Advanced
mprycmpryc

backup-etcd

Create and store OpenShift etcd snapshots with retention and metadata.

Community
Advanced
yaacovyaacov

check-ocp-health

Diagnose OpenShift cluster health issues and provide kubectl remediation commands.

Community
Advanced