check-cluster-health

Name: check-cluster-health
Availability: InStock
Author: lloydchang

Assess health of multi-cloud Kubernetes clusters across AWS EKS, Azure AKS, and Google GKE.

2|1|Updated Mar 11, 2026

Search Tags:#automation #monitoring #kubernetes #multicloud #health-checks

Ready to run

npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill check-cluster-health-lloydchang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-cluster-health
Source: https://github.com/lloydchang/agentic-reconciliation-engine/tree/main/core/ai/skills/check-cluster-health
Command: npx skills add https://github.com/lloydchang/agentic-reconciliation-engine --skill check-cluster-health-lloydchang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, azure-identity, azure-mgmt-containerservice, azure-mgmt-monitor, google-cloud-container, google-cloud-monitoring, kubernetes, typer, pydantic, and includes scripts (resource) components.

What problem does it solve?

Multi-cloud Kubernetes environments often have fragmented health data, making it hard to detect issues quickly. This Skill provides automated, unified health checks across AWS EKS, Azure AKS, Google GKE, and on-prem clusters to drive reliable operations.

Core Features & Use Cases

Node, pod, service, storage, networking, security, and performance health checks across providers
Centralized reporting with per-cluster drill-down for troubleshooting and compliance
Cross-cloud health orchestration to scale checks across many clusters

Quick Start

Run the health check for a cluster by specifying its name and provider to generate a multi-cloud health report.

Frequently Asked Questions about check-cluster-health

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

FAQPage Schema

How do I automate multi-cloud Kubernetes health checks across AWS EKS, Azure AKS, and Google GKE?▼

Automate multi-cloud Kubernetes health checks by running a Python script that uses provider SDKs like boto3 and azure-mgmt-* to collect and evaluate node, pod, and network status. This generates a centralized health report for troubleshooting and compliance.

What Kubernetes resources are evaluated during an automated cluster health assessment?▼

An automated cluster health assessment evaluates node, pod, service, storage, networking, security, and performance health data. It uses a cluster health handler framework to collect, evaluate, and summarize this data for per-cluster drill-down reporting.

Do I need specific Python provider SDKs to monitor Kubernetes clusters across multiple clouds?▼

Yes, monitoring Kubernetes clusters across multiple clouds requires Python 3.8+ and specific provider SDKs including boto3, azure-mgmt-containerservice, azure-mgmt-monitor, google-cloud-container, and google-cloud-monitoring to collect health data.

Can I orchestrate cross-cloud health checks for many on-prem and managed Kubernetes clusters?▼

Yes, you can orchestrate cross-cloud health checks for many on-prem and managed Kubernetes clusters. This scaling capability allows unified health assessments across AWS EKS, Azure AKS, Google GKE, and on-prem environments.

Why does multi-cloud Kubernetes environments often have fragmented health data and how to centralize it?▼

Multi-cloud Kubernetes environments have fragmented health data because metrics are isolated within individual provider dashboards. Centralize this data by applying a unified health handler framework to collect and summarize cluster statuses into a single report.

Does this approach to Kubernetes health monitoring require a cluster health handler framework?▼

Yes, this approach to Kubernetes health monitoring requires a cluster health handler framework to properly collect, evaluate, and summarize health data across different providers, ensuring reliable operations and accurate centralized reporting.