Health Check Monitor

Edge Cases

• Multi-tenant Clusters: Namespaces may have different monitoring requirements
• StatefulSets: Different health criteria than stateless deployments
• Custom Resources: CRDs may need special health checks

Inputs

• cluster: Target cluster name (optional, default: current context)
• namespace: Namespace to monitor (optional, default: all)
• check_types: Types of checks to perform (optional, default: all)
• alert_thresholds: Custom alert thresholds (optional)

Process

1. Cluster Discovery: Identify target clusters and namespaces
2. Resource Collection: Gather pod, node, and service status
3. Health Assessment: Evaluate health metrics against thresholds
4. Alert Generation: Create alerts for issues found
5. Report Generation: Produce monitoring summary and recommendations

Outputs

• Health Status: Overall cluster health score and status
• Resource Metrics: CPU, memory, and storage utilization
• Alert Summary: List of active alerts and recommendations
• Trend Analysis: Resource usage patterns over time

Scripts

• scripts/health-checker.py: Main monitoring implementation
• scripts/alert-handler.py: Alert generation and notification
• scripts/metrics-collector.py: Resource metrics gathering

Trigger Keywords

health, monitor, kubernetes, cluster, alert, resources, nodes, pods

Human Gate Requirements

• Critical Alerts: High-severity issues require immediate attention
• Resource Limits: Actions requiring resource changes need approval

References

• references/kubernetes-health-patterns.md: Health check methodologies
• assets/alert-templates/: Alert message templates
• examples/cluster-configs/: Sample cluster monitoring configurations