Maestro ManifestWork Tracer FAQs

Question 1

How do I find a Resource ID if I only have a manifest name?

Accepted Answer

The skill searches the management cluster for the manifest, identifies its AppliedManifestWork owner, and extracts the manifestWorkName which corresponds to the Resource ID.

Question 2

What is the difference between a Work Name and a Resource ID in Maestro?

Accepted Answer

A Work Name is user-defined via the gRPC client, while the Resource ID is the internal database primary key and CloudEvent identifier used by the Maestro system.

Question 3

Can I use this skill with separate kubeconfig files?

Accepted Answer

Yes, the skill provides specific workflows for using separate kubeconfig paths, multiple contexts within one file, or merging files for easier access.

Question 4

Why does this skill require access to two different clusters?

Accepted Answer

Maestro uses a dual-cluster architecture where the Service cluster hosts the database and server, while the Management cluster hosts the agent and the actual applied manifests.

Question 5

How does this skill relate to the trace-resource-request skill?

Accepted Answer

This skill identifies 'what' resources exist (IDs and manifests), while trace-resource-request uses those IDs to debug 'why' a request may have failed in the log flow.

Maestro ManifestWork Tracer

Key Features

Use Cases

Maestro ManifestWork Tracer

Key Features

Use Cases