skills.rest
openshift-online
openshift-onlineOFFICIAL
Explore all skills by this author →
WebsiteGitHub

trace-manifestwork

Trace ManifestWork lifecycles across Maestro clusters via kubectl and jq.

20|48|Updated Nov 9, 2023
Search Tags:#debug#trace#kubectl#multi-cluster#ManifestWork#AppliedManifestWork#Maestro
One-click install
npx skills add https://github.com/openshift-online/maestro --skill trace-manifestwork
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace-manifestwork
Source: https://github.com/openshift-online/maestro/tree/main/.claude/skills/trace-manifestwork
Command: npx skills add https://github.com/openshift-online/maestro --skill trace-manifestwork

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill helps trace ManifestWork resources through the Maestro system to find relationships between user-created work names, database resource IDs, and applied manifests, or to debug manifest application issues across the management cluster and database.

Core Features & Use Cases

  • Bidirectional tracing between: User-created work name, Database Resource ID, AppliedManifestWork, and deployed manifests
  • Cross-cluster visibility: query service cluster (database) and management cluster (AppliedManifestWorks and manifests) to assemble a complete trace
  • Debug lifecycle issues: creation, update, and deletion flows, including verification of what was applied vs. what exists in the cluster
  • Use Case examples: determine resource ID from a work name, locate the AppliedManifestWork for a manifest, or verify what manifests are tied to a work

Quick Start

  • Trace by Resource ID: .claude/skills/trace-manifestwork/scripts/trace.sh --resource-id "<resource-id>"
  • Trace by Manifest: .claude/skills/trace-manifestwork/scripts/trace.sh --manifest-kind deployment --manifest-name maestro-e2e-upgrade-test --manifest-namespace default --svc-context <svc-context> --mgmt-context <mgmt-context>
  • Trace by User Work Name: .claude/skills/trace-manifestwork/scripts/trace.sh --work-name "<work-name>"

Frequently Asked Questions about trace-manifestwork

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

FAQPage Schema
How do I trace a ManifestWork resource across Maestro clusters?▼

Trace ManifestWork resources by correlating user work names, database resource IDs, and AppliedManifestWorks using the trace script with kubectl and jq. Entry points include resource ID, manifest details, or work name, returning a complete cross-cluster trace linking service and management clusters.

Can I debug manifest application issues across management and service clusters?▼

Yes, this skill enables debugging of manifest lifecycle issues—creation, update, deletion—by querying both the database and cluster state to verify what was applied versus what exists, surfacing discrepancies across clusters.

How do I find the resource ID or AppliedManifestWork for a deployment?▼

Use bidirectional tracing to correlate user-created work names with database resource IDs and deployed AppliedManifestWorks. Query by manifest kind, name, and namespace across service and management contexts to locate relationships.

What tools do I need to trace ManifestWork lifecycles?▼

Tracing ManifestWork requires kubectl for cluster access, jq for JSON processing, and script-based queries to the database. Both service cluster and management cluster contexts are needed for complete cross-cluster visibility.

Why would I need to trace ManifestWork instead of querying individual clusters?▼

ManifestWork tracing correlates relationships across distributed systems—linking work names to database IDs to applied manifests—revealing the full lifecycle in one view, rather than piecing together isolated cluster queries.

Related Skills

Explore More Software Engineering Skills→
rohitg00rohitg00
944

k8s-certs

Automate Kubernetes certificate management with cert-manager for issuers and certificates.

Community
Advanced
vfarcicvfarcic
2

dot-ai-remediate

Analyze Kubernetes cluster issues to identify root causes and remediation steps.

Community
Advanced
luiscamaralluiscamaral
1

l0-infrastructure

Automate L0 infrastructure provisioning with Talos Linux and Proxmox Terraform deployments.

Community
Advanced
huynguyenhhuynguyenh
3

hnh-k8s

Run kubectl commands to debug and monitor Kubernetes EKS clusters.

Community
Intermediate