Diagnose Maestro Deployment

Diagnoses failed Maestro cluster deployments by analyzing Helm releases, pod status, and resource conflicts

majiayu000 b010ff9 2 files · 1.9 KB Updated 567 repo stars

File contents

Diagnose Maestro Deployment

Automatically diagnoses failed Maestro cluster deployments by:

  • Analyzing deployment output to identify resource groups and cluster names
  • Checking Helm release status in both service and management clusters
  • Inspecting pod states and error conditions
  • Identifying resource conflicts and timing issues
  • Generating a detailed analysis report with root cause and recommendations

Prerequisites:

  • Azure CLI installed and logged in
  • kubectl and kubelogin installed
  • Access to the failed deployment output or cluster information

Usage:

# Diagnose using deployment output file
diagnose-maestro-deployment /path/to/deployment.output

# Diagnose using cluster names directly
diagnose-maestro-deployment --svc-rg <resource-group> --svc-cluster <cluster-name> --mgmt-rg <resource-group> --mgmt-cluster <cluster-name>
#!/bin/bash
# Execute the diagnostic script
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
exec "$SCRIPT_DIR/scripts/diagnose.sh" "$@"

majiayu000/claude-skill-registry-data/tree/main/data/diagnose-maestro-deployment commit b010ff980c

Frequently asked questions

npx skillmds add majiayu000/diagnose-maestro-deployment