debug-capz-k8s

Diagnose CAPZ Kubernetes cluster failures using Prow artifacts, kubectl, and az CLI.

334|482|Updated Jun 12, 2018
One-click install
npx skills add https://github.com/kubernetes-sigs/cluster-api-provider-azure --skill debug-capz-k8s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-capz-k8s
Source: https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/.claude/skills/debug-capz-k8s
Command: npx skills add https://github.com/kubernetes-sigs/cluster-api-provider-azure --skill debug-capz-k8s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive approach to diagnosing and resolving failures in CAPZ (Cluster API Provider Azure) managed Kubernetes clusters, reducing downtime and troubleshooting time.

Core Features & Use Cases

  • Multi-faceted Debugging: Integrates live cluster inspection (kubectl), VM-level diagnostics (az CLI), Prow/GCS artifact analysis, and build log triage.
  • Deep CAPZ Knowledge: Understands CAPZ template flavors, E2E test structures, addon deployments (Calico, cloud-provider-azure, CSI), common failure patterns, and transient errors.
  • Use Case: When a CAPZ-provisioned workload cluster fails to become ready, this Skill can analyze Prow job logs, inspect the control plane and worker node VMs via az CLI, and examine CAPI resource states to pinpoint the root cause, whether it's infrastructure, networking, or bootstrapping issues.

Quick Start

Use the debug-capz-k8s skill to analyze the failing CAPZ E2E test run from the provided Prow URL.

Frequently Asked Questions about debug-capz-k8s

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

FAQPage Schema
How do I troubleshoot a CAPZ Kubernetes cluster that fails to become ready?

Diagnosing CAPZ cluster failures requires analyzing Prow job artifacts, inspecting live cluster states via kubectl, and examining Azure VM configurations via az CLI to pinpoint root causes across infrastructure, networking, or bootstrapping layers.

What causes worker node bootstrapping failures in Cluster API Provider Azure?

Worker node bootstrapping failures in Cluster API Provider Azure typically stem from CNI addon deployment errors, infrastructure provisioning delays, or Azure VM configuration issues, diagnosed by inspecting CAPI resource states and VM-level diagnostics via az CLI.

How do I analyze Prow job artifacts to debug Kubernetes E2E test failures?

Analyzing Prow job artifacts to debug Kubernetes E2E test failures requires reviewing build logs and GCS artifacts to correlate transient errors, addon deployment failures, or CAPZ template flavor mismatches with E2E test structures.

Can I use kubectl and az CLI together to debug control plane initialization issues in CAPZ?

Yes, using kubectl to inspect CAPI resource states and az CLI to examine Azure VM configurations together debugs control plane initialization issues in CAPZ by correlating Kubernetes API server health with underlying Azure infrastructure status.

Why does my CAPZ managed Kubernetes cluster have CNI or CCM addon deployment problems?

CNI or CCM addon deployment problems in a CAPZ managed Kubernetes cluster typically arise from cloud-provider-azure integration failures, Calico misconfigurations, or transient errors during bootstrapping, identifiable through live cluster inspection and Prow job log triage.

What are common failure modes in Cluster API Provider Azure infrastructure provisioning?

Common failure modes in Cluster API Provider Azure infrastructure provisioning include Azure VM creation delays, control plane initialization timeouts, and resource hierarchy misconfigurations, requiring CAPZ architecture knowledge and az CLI diagnostic output analysis to resolve.