diagnose-maestro-deployment

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

20|48|Updated Nov 9, 2023
One-click install
npx skills add https://github.com/openshift-online/maestro --skill diagnose-maestro-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-maestro-deployment
Source: https://github.com/openshift-online/maestro/tree/main/.claude/skills/diagnose-maestro-deployment
Command: npx skills add https://github.com/openshift-online/maestro --skill diagnose-maestro-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires az, kubectl, helm, jq, python3, kubelogin, and includes scripts (resource) components.

What problem does it solve?

This Skill diagnoses failed Maestro cluster deployments by analyzing deployment outputs, Helm release statuses, pod health, and potential resource conflicts to identify root causes and actionable remediation steps.

Core Features & Use Cases

  • Analyze deployment output to extract cluster, resource group, and cluster names.
  • Verify Helm releases across service and management clusters and inspect pod states.
  • Detect resource conflicts and timing issues, generating a structured diagnosis report.
  • Real-world Use Case: When a Maestro deployment fails in a multi-cluster setup, run this skill to generate a prioritized root-cause analysis and remediation steps for operators.

Quick Start

diagnose-maestro-deployment <path-to-deployment-output> or diagnose-maestro-deployment --svc-rg <rg> --svc-cluster <name> --mgmt-rg <rg> --mgmt-cluster <name> Examples:

  • diagnose-maestro-deployment /path/to/deployment.output
  • diagnose-maestro-deployment --svc-rg hcp-underlay-pers-usw3-svc --svc-cluster pers-usw3-svc --mgmt-rg hcp-underlay-pers-usw3-mgmt-1 --mgmt-cluster pers-usw3-mgmt-1

Frequently Asked Questions about diagnose-maestro-deployment

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

FAQPage Schema
How do I diagnose a failed Maestro deployment in Azure AKS?

Diagnose failed Maestro deployments by analyzing Helm releases, pod status, and resource conflicts across your Azure AKS clusters. Run diagnose-maestro-deployment with your deployment output or cluster details to generate a structured root-cause analysis and remediation steps.

Can I use this tool to troubleshoot multi-cluster Maestro setups?

Yes. This tool is designed for multi-cluster Maestro setups on Azure AKS. It verifies Helm releases and pod states across both service and management clusters, detecting conflicts and timing issues to identify deployment failures.

What do I need to run Maestro deployment diagnostics?

You need Azure CLI (az), kubectl, Helm, jq, Python3, and kubelogin installed. The tool accepts either a deployment output file or explicit resource group and cluster names for both service and management clusters.

How do I interpret the diagnosis report output?

The diagnosis report provides a prioritized root-cause analysis with actionable remediation steps. It identifies Helm release failures, pod health issues, and resource conflicts, structured so operators can address the highest-impact problems first.

Does this work if my deployment output file is incomplete?

The tool can work with incomplete deployment output. As an alternative, provide explicit cluster and resource group parameters (--svc-rg, --svc-cluster, --mgmt-rg, --mgmt-cluster) to query live cluster state directly.