cluster-resource-health

Name: cluster-resource-health
Availability: InStock
Author: CNOE

Query EKS clusters via kubectl and report pod, node, and resource health.

392|73|Updated Jun 12, 2025

Search Tags:#monitoring #kubernetes #eks #cluster-health #resource-utilization #pod-status #node-conditions

Ready to run

npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill cluster-resource-health

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cluster-resource-health
Source: https://github.com/cnoe-io/ai-platform-engineering/tree/main/ui/src/skills/cluster-resource-health
Command: npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill cluster-resource-health

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified visibility into Kubernetes cluster health across EKS environments, enabling teams to detect pod failures, node issues, and capacity risks early.

Core Features & Use Cases

Cluster-wide overview: aggregated pod statuses, node conditions, and resource utilization for quick triage.
Drill-down insights: per-namespace, per-node health summaries with actionable alerts.
Use Case: run during capacity planning or incident response to identify failures and forecast headroom for new workloads.

Quick Start

Query all configured EKS clusters to produce a real-time health dashboard detailing pods, nodes, and resource usage.

Frequently Asked Questions about cluster-resource-health

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

FAQPage Schema

How do I monitor Kubernetes cluster health across EKS environments?▼

Kubernetes cluster health monitoring aggregates pod statuses, node conditions, and resource utilization across EKS environments by querying clusters via kubectl to produce structured dashboard outputs.

What is the best way to check pod status and node conditions for capacity planning?▼

Checking pod status and node conditions for capacity planning involves running a cluster-wide health query that aggregates per-namespace and per-node metrics to forecast headroom for new workloads.

Can I get a per-namespace health summary during an EKS incident response?▼

Yes, you can generate per-namespace and per-node health summaries with actionable alerts during incident response by running a drill-down query to identify pod failures and node issues early.

Do I need kubectl to read node and pod metrics for a cluster audit?▼

Yes, querying clusters via kubectl and reading node and pod metrics are required to perform cluster audits and produce real-time health outputs for production and staging environments.

How does resource utilization reporting work for staging and production clusters?▼

Resource utilization reporting works by querying configured EKS clusters to aggregate node and pod metrics, producing a real-time dashboard detailing capacity risks for production and staging environments.